VI Analyzer Test deployment - packages

[James_W]

Just a note / comment.

NI Package Builder seems deficient in the ability to deploy tests for VI Analyzer (as NI PM is unable to deploy to vi.lib or the LabVIEWData folder) this seems frankly stupid.

Luckily JKI VIPM is able to do this and actually does a proper prebuild process, updating the files list in the source folder after pre-build before it actually builds the package (unlike the LabVIEW exe build). When are NI going to support maintenance of VI Analyzer tests in house? (My current employer is not keen on having VIPM on machine in case it's used to mess with the source files and multiple projects are opened at once out of necessity)

[James_W]

Ok ....

I've got that wrong...

Attempting to build an LLB in JKI's VIPB and then deploy it seems to result for me in an error.
The LLB is exactly the same as it was before I converted it back to source folders & VIs (at least from what I can see), and has no errors, but VI Analyzer throws error 7 on attempting to load the test VI...

Thoughts?

[Hooovahh]

When I saw your post I thought they must have fixed something in VIPM, because I had a hard time making a VIA package.  I did eventually get it working but it was a hack. Pre build will zip all the VIA Tests into a zip, then Pre-Install VI will decompress them.  This means VIPM doesn't relink or mass compile.  I can't remember if there were extra things to make it work. I tried disabling mass compile but that didn't work.

[Darren · Accepted solution]

I recommend deploying your VI Analyzer tests as folders that are named [test name].llb. That way you don't have to try to convert things to LLBs as part of the build process.

You can see that the VI Analyzer tests in the LVAddons folder are deployed in this way:

C:\Program Files\NI\LVAddons\viawin\1\project\_VI Analyzer\_tests

[James_W]

yup, the folder naming folder.llb trick solved it very nicely thanks Darren