09-09-2011 10:46 AM
I released a production test application last month and began work on another project that is similar, but not similar enough to try to make the first program handle both products. So I copied the entire project, made the many modifications that I needed and built an Application and Installer. The installer put my new program where I wanted it but it deleted the executable made from the original project. I've tried to reinstall the original but the installer stops after informing me that a newer version of the program already exists. I'm guessing that it's referring to the new program.
I've inspected the build specifications of both and can't see anything that ties them together. What am I doing wrong?
Solved! Go to Solution.
09-12-2011 12:39 PM
Hey Jim,
When you copied your new project over did you update the output path associated with the installer? When I do this on my machine the path for the installer still points to the Original Project and has to be updated. I would also take a look at this KB: http://digital.ni.com/public.nsf/allkb/7512140C7C9D0C5F86256CC2007B722A?OpenDocument Each LabVIEW installer uses an Upgrade Code which Microsoft uses to associate the two installers. The KB outlines how to fix this for instances where you want to copy the project. There are also some other issues that can arise from copying projects that are here and may be applicable: http://zone.ni.com/devzone/cda/tut/p/id/7197
Please post back if this solves your issue or if you have any additional questions.
09-12-2011 02:59 PM
@Kevin_F wrote:
Hey Jim,
[...] I would also take a look at this KB: http://digital.ni.com/public.nsf/allkb/7512140C7C9D0C5F86256CC2007B722A?OpenDocument Each LabVIEW installer uses an Upgrade Code which Microsoft uses to associate the two installers. [...
I duplicated the Installer build specification and Bob is now my uncle. Thank you.