LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Share a single initialization file

I am running Labview 8.2.1. I have two programs that I want to share the same initialization file. One program is the usual operator program and the second program is essentially the same program with some added features (I basically unhide a few control). The features will allow me to update various portions of the intialization file to be used by the operators.
 
Ideally I would like to have a single installation program that will install both programs. The programs will have different names. If I use the same directory (previous version of Labview), it will generate a dll error when it builds the program (both generate a dll file with the same name).
 
Any thoughts will be appreciated.
0 Kudos
Message 1 of 2
(2,499 Views)
I am not sure how to solve your installation creation problem, this is more advice that maybe you should not be trying to solve the problem this way.

Just guess here, but having two separate applications probably means you have two separate main VIs (that are very similar as you mentioned).
This may work fine in the beginning, i.e. your application is stable and then you hide/show some controls and save a copy as a new VI, but eventually you will reach a point (as more and more *features* get added in) where it will just become extremely troublesome to have two separate VIs, and each time to build two binaries.

Instead, why don't you have some form of user login, and have the controls dynamically disabled/enabled depending on whether a user/superuser is logging in. That way you only need to design/maintain one main VI and it makes further improvement down the line much easier.

Neil
Message 2 of 2
(2,487 Views)