LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Can we build two installers (each installs different .exe) in the same Labview Project?

Solved!
Go to solution

Hello there,

 

Since there are many common files between the two test programs, I built two applications in the same project. Then I need to build two installers for the applications accordingly. I'm having trouble to add the second application into the second installer when I specify the source files in the installer properties. When I select that application pack under Build Specifications, I can't add it to the destination folder for the installer. When I have the second application pack and the destinatioin folder both selected, the top arrow (to add files from the left pane to the right pane) turns into grey (un-clickable). However, I found that If I select the first application pack under Build Specifications, the arrow turns live. But I don't want to add the first application to my second application installer.

 

Can anybody understand what I'm talking about? Looking forward to your help!

 

Thanks so much!

Spring

0 Kudos
Message 1 of 9
(3,871 Views)

If you want to build a second installer, you need to create a new installer build specification.

 

It is definitely possible to have multiple installer build specifications in a project and you can choose which executable build specifications go into each. I've even created multiple versions of the installer - one with all of the prerequisites required (e.g. runtime engine and drivers) and a 'lightweight' version which just includes my executable.


LabVIEW Champion, CLA, CLED, CTD
(blog)
0 Kudos
Message 2 of 9
(3,864 Views)

Hi Sam,

 

Under Build Specifications in my project, I have the following:

 

application 1

installer 1

application 2

installer 2

 

Please advise.

 

Thanks,

Spring

 

0 Kudos
Message 3 of 9
(3,851 Views)

That is correct, what is the actual problem you are having? Just assign Application 1 to Installer 1 and Application 2 to Installer 2 under the Source Files pane of the build specification:

2015-09-29_16-51-46.png


LabVIEW Champion, CLA, CLED, CTD
(blog)
0 Kudos
Message 4 of 9
(3,844 Views)

Hi Sam,

 

I deleted the destination folder and re-created it. It allowed me to add application2 to installer2. However, when building it, It gave me error saying can't add application1.exe. But I didn't specify application1 in installer2 at all. Once the error appears, the destination folder became empty and I couldn't specify application2 in installer2 anymore. Very strange.

 

Thanks,

Spring

0 Kudos
Message 5 of 9
(3,811 Views)

Oh, are you trying to install both executables to the same destination folder? That might not be possible (it might make things messy when installing/uninstalling).

 

I suggest you try to put the executables into different destination folders. I would also check the names of each executable and the build location as well (where the executables go after being compiled - before you do the installer).

 

Can you take a screenshot of the Source Files page for each of your installers?


LabVIEW Champion, CLA, CLED, CTD
(blog)
0 Kudos
Message 6 of 9
(3,776 Views)

Hi Sam,

 

Thanks Sam for trying to help! I've been using different names and different destinations. Since I tried so many times and couldn't get it working (even tried to restart Labview, restart the PC, etc), I decided to remove installer2 from the project. Then I re-created installer2 from scratch (not by duplicating installer1 then making changes) and it worked!

 

It looks like duplicating installer then making changes won't work -- although the changes (i.e. specifying Application2 in Installer2 and exclude Application1 from Installer2, etc.) can be saved in the properties but when building the installer,  it gives you error saying can't add Application1 to Installer2 (seems it doesn't recognize your changes). After the building failure, all the files you specified in Installer2 are gone. I tried so many times, it all ended up with the same failure.

 

So the question to National Instruments is: Why doesn't it reject the changes in the first place?

 

Regards,

Spring

0 Kudos
Message 7 of 9
(3,753 Views)

Perhaps a stupid suggestion, but if you duplicated the installer, did you change the product ID hash? In one of the pages of the build specification page is a code which is used to uniquely identify the 'product' that's being installed. I don't think it should have any difference on the build itself but it might have caused you problems when you actually came to install it.


LabVIEW Champion, CLA, CLED, CTD
(blog)
0 Kudos
Message 8 of 9
(3,732 Views)
Solution
Accepted by topic author 2014spring

Hi Sam,

 

I went through all the pages and didn't see any product ID. Which page do you see harshed product ID?

 

The problem I had was on the build itself. I had not gone far enough to install it. 🙂

 

After removing the duplicated installer and created a new one from scratch, everything worked as expected (from build to installation to running the program).

 

Regards,

Spring

0 Kudos
Message 9 of 9
(3,728 Views)