LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

What forces an uninstall prior to installing a new application?

Created application "A" and distribution kit using LabWindows/CVI 6.0. Installed on another PC. Created modified application "B" by cloning "A". Changed names of all files, distribution kit, installation path, group names, etc. Basically everything thing that was named "A" is now named "B". When I attempt to install "B" on the PC, the installer insists on removing "A" first. What is causing this? These should be two independant applications with different names and paths. Any insights would be greatly appreciated. Thank you. Scott T.
0 Kudos
Message 1 of 4
(2,633 Views)
Scott,

When you cloned the first application, you probably copied the project file. The project file contained the GUID that the installation system uses to identify the application. So even though you later changed everything about it, the installer still believes this to be the same application.

With version 6.0 of CVI, the only way to work around this is to open the project file of "B" in a text editor (making sure CVI doesn't have that file opened at the same time) and replace the GUID in the "Distribution Kit GUID" value of the "[Distribution Kit]" section with a new one. Then you'll need to regenerate the distribution kit of "B", which you should be able to install in the same PC as application "A"

Let me know if you're not sure what a GUID is or if you'
re not sure how to generate a new one.

Luis
NI
0 Kudos
Message 2 of 4
(2,633 Views)
In fact, you don't need to replace the GUID, you only need to delete the line containing the GUID - CVI will then generate a new one for you the next time you build a dist kit.

Martin.
--
Martin
Certified CVI Developer
0 Kudos
Message 3 of 4
(2,633 Views)
The MSI installer uses a unique GUID generated when the distribution kit was originally created. Renaming files doesn't change the GUID.
You can solve your GUID problem and save yourself a lot of renaming trouble by creating your application "B" within CVI by doing a File >> Save Project As...
If you save your project under a new name (using File >> Save Project As... in the project window) , you'll get a new GUID when you build a distribution kit using the new project. Rather than updating two projects with every change, do all your development in one project. Every time you're ready to release both versions, do another File >> Save Project As...
0 Kudos
Message 4 of 4
(2,633 Views)