LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Application Builder Issue (V8.5)

Solved!
Go to solution

I built a vi, which is a fairly large program, and built an installer with the Application Builder. It installs and works fine.

 

I created another version of the program by modifying the vi slightly (renaming it of course) and created another exe and installer (with different names and install locations, of course). That also works fine.

 

Now here’s the problem: When I install the modified program, it creates the new folder and installs all the files fine (the exe and all my other files and folders that I directed the installer to install and create). HOWEVER it deletes all the files and folders in the OTHER (first vi exe) folder. (Those two folders are in the same parent folder, but that should not matter.) It also deletes the desktop shortcut that the first installer created, and puts the new shortcut (the shortcut icons are also different) on the desktop. If I re-run the first installer, it does the same thing: It deletes the other files and desktop shortcut and creates the first files, folders, and desktop icon. So, in other words, the last installer to run takes priority. Apparently the installer thinks each installer replaces (and uninstalls) the other. How strange! (I have installers for other vi’s and they are not affected.)

 

Does anyone know what the problem may be?

 

Thanks all,

Ed

0 Kudos
Message 1 of 3
(2,383 Views)

Ed,

 

please check if the build scripts for installer use the same "Upgrade Code". I never encountered that this leads to uninstallation of components, but i dont know what the Microsoft Installer does in the background.....

 

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 2 of 3
(2,352 Views)
Solution
Accepted by topic author Edjsch

I search ni.com for "DistributionGUID" and found this article: http://digital.ni.com/public.nsf/allkb/1D9D2C81AD2007AC8625758D0050E68B

 

I did the first method of duplicating the exe and it created a "Copy of" it. Then I removed the first from the project. Then I renamed the exe without the "Copy of", but that didn't work. The DistributionGUID was still the same. Maybe I missed something.

 

So instead, I built both the exe and installer with the "Copy of". That generated a new DistributionGUID. Then I duplicated that, went back to the original name, and thank goodness, it created still another DistributionGUID.

 

Now I can install both with out disturbing the other. All is well again.

 

BTW, I had a similar post last year: http://forums.ni.com/t5/LabVIEW/Installer-built-with-Application-Builder-gives-error-quot-Cannot/td-... however my version, V8.5, does not have the "Generate" button to generate a new DistributionGUID in the "Upgrade Code" box. That would have made things much simpler!

 

Cheers! Smiley Happy

0 Kudos
Message 3 of 3
(2,333 Views)