LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Application instance change in 8.2

Salut.

I have been using an home made deploying tool since LabVIEW 6.x.

Somewhere along the deployment, the tool does a save as on the source code of the deployed software. The deployment tool and the deployment software are both link to a library of VIs.

In LV6 and 7, i had to rename all the VIs used by the deployment tool in order for the save as to work because of the unique name in memory rules of those versions.

In LV8 i did not have to do this because my deployment tool was running in the "NI.LV.Dialog" application instance and the save as was working.

Now in LV8.2, it seems that it does not work anymore, i get an error stating that the VI cannot be saved in the current state. And i get this error on the shared VIs.

Is there a work around, or will i have to revert to doing a mass duplicate save as for the deployment tool VIs?
0 Kudos
Message 1 of 2
(2,484 Views)
jacemdom,

I am not really clear on what is going on.

Is your deployment tool written in LabVIEW? If so, which version?

When you say a "library of VIs" are you referring to an llb?

What do you mean by the "NI.LV.Dialog" application instance?

Is it possible to create a simple project that shows the saving problem?

Is it possible to include a screenshot of the error you are seeing?

Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me 🙂
0 Kudos
Message 2 of 2
(2,462 Views)