Mass compile / defer decision

[jvh75021]

When trying to do a deployment in TestStand I got errors about changed VIs that weren't saved. They weren't saved because I didn't want to save the changes and TestStand crashed (again). Searching the TestStand forum it seems I need to perform a mass compile. If a mass compile is done what is compiled, the original version or the changes I did not want to save?

Is there any chance that NI will change this maddening feature to allow quitting without saving  or deferring?

thanks,

jvh 

[Eric_B.]

jvh,

The reason that it is asking you to save is because the deployment utility is making modifications to your VIs and their sub-VIs to make sure everything is in a compatible version for deployment.  What are your adapter settings on this development machine? (using LabVIEW RTE or LabVIEW development system?)

What VIs are the utility asking you to save?  If we know that, we can better figure out why changes are being made to these VIs and give a recommendation on whether or not it's ok to just save the changes to make everything work as expected.

[jvh75021]

Thanks for posting.

Using a development system. Could you expand on your question about adapter settings? Sorry but I got around it somehow Wednesday night and did not keep a list of what the problem vis were.

jvh 

[Eric_B.]

I was asking about adapter settings because I was under the impression that changed the behavior of the Deployment Utility, but that is not actually the case.

When you use the Deployment Utility, you have to have the LabVIEW Development Environment installed, and whatever version is active (the one that was opened most recently) will be used to build the deployment.  During the build process, the code modules are all saved up to that current version, which may have caused your problem before, but I'm glad to hear that it's all worked out now.