LV8.6 executable using shared variables

[Al1234]

I am programmatically deploying some shared variables for use in an executable. I can only get this to work if the shared variable llb is placed in the support folder.

Ideally I just want an exe file with no customer-accessible files in the support folder. Is it possible to include the shared variable llb inside the exe and still successfully deploy them?

Thanks

Al

Vista 32-bit LabVIEW 8.6

[Sletten]

Hello AI

I have done a bit of testing on 8.6 aswell regarding shared variables and it entailed pretty much the same results as you have stated. However if you manage to deploy your shared variable programmatically and thereafter edit your application (removing the deployment invoke node) and edit your build properties to include the shared variable llb in the executable instead of the support directory, rebuild and then run it you can acutally still get the shared variable without redeploying (you should be able to see the shared variable is still deployed in the distributed system manager). The downside to this is that the second you need to add another variable you will have to redeploy meaning editing your application/build properties which makes it a bit hard to work with.

I seems that the proper solution to your problem has been introduced in Labview 2009, I have tested the guidelines here and this works much smoother than the extensive things you have to do in 8.6.

hope it helps 🙂

Sletten

[Al1234]

Thanks! I'll have a play.

Is this method robust enough for use with an exe given to a customer?

Al

[Sletten]

Hi Al

That kinda depends on what you are using the shared variables for in your application. I would be careful if your using 8.6 as this could entail some unforseen challenges with updates, added features etc.

Furthermore I have only tested the shared variables on the closed network at work, perhaps there could be some problems with the firewalls.

Sletten

[Al1234]

OK - The shared variables are only used to connect two VIs locally (same PC) for a simulator used when the DAQ isn't present. So I'll try it...