LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade to LabVIEW 2012 caused Additional Installers issue

Solved!
Go to solution

Okay, I'll give that a shot, thank you!  I'm so glad there is a better way.  🙂

0 Kudos
Message 11 of 15
(428 Views)

Doug,

 

I finally had time to try your method (sorry for the delay), but unfortunately it did not fix the problem of not being able to build the installer on another computer.

 

Forced-reinstall seemed to work on my computer, although I didn't notice any particular difference myself.  I saved a copy of the project file (so that I could modify it - the original is under source control at this point), then changed a setting and saved it then restored that setting and saved it, in case it would save any differently, but nothing in the file changed from the original project file which I had given to my coworker.

 

In order to verify that the issue would happen again, I went to another computer.  This one had my application installed on it already, including VISA Runtime 5.2, and then I installed the LabVIEW Developer Suite 2011 (which includes LabVIEW 2010 SP1).  Then I opened up my project and built the executable and tried to build the installer.  This time I got a request for "NI LabVIEW Run-Time Engine 2010 SP1" and "NI-VISA Runtime 5.2", both on the disk "FADEC_Emulator..." (see attached screenshot).  I could possibly see it asking for the VISA Run-Time only because it might not have the installer to build into my app's installer (despite the runtime itself already being installed on the computer), but how could it possibly not have the LabVIEW Run-Time?

 

The properties of the installer showed NI-VISA Runtime 5.2 selected as I would expect when viewed on that computer.

 

I am attaching my project file because I don't think there is much useful information in the way of company secrets, and maybe looking at it will allow you to tell what is going wrong.  I had to rename the extension from ".lvproj" to ".txt" because the forum gave me an error about the content type not matching the file extension.

 

Please let me know if you have any other ideas as to what is going on, and thank you again for your help.

 

-Joe

Download All
0 Kudos
Message 12 of 15
(415 Views)

Hey Jim,

 

Thanks for the update. Regarding building the installer on another PC, you will actually need the full version of VISA and not just the runtime due to the external resources that are only available in the full version of VISA. As for the LabVIEW 2010 SP1 Run-Time Engine, LabVIEW Development Suite 2011 does not actually include 2010 SP1, and so you will have to download the LabVIEW 2010 SP1 Run-Time Engine (http://joule.ni.com/nidu/cds/view/p/id/2292/lang/en ) due to dependencies from your project that are inherent to the original build environment, 2010 SP1. Please let me know if you run into any other issues with distributing your build.

 

Doug W

Applications Engineer
National Instruments
0 Kudos
Message 13 of 15
(390 Views)

Doug,

 

I'm Joe, not Jim.  Smiley Wink

 

The NI Developer Suite 2011 DS1 box that I got in the mail from NI on February 21st, 2011 as part of my service plan includes LabVIEW Professional Development System version 2010 SP1, according to both my experience and the card that lists the NI Developer Suite Core Components that came in the box.  That is what I installed on the most recently computer that then said it didn't have the 2010 SP1 run-time.

 

Separate from that discrepency, why would it ask for those items on a disk with my application name?  Did anything look funny in that LabVIEW project file that I posted?  Or was it not helpful?

 

Thanks for your help,

 

-Joe

0 Kudos
Message 14 of 15
(387 Views)

Hi Joe,


I conferred with my colleagues and I was mistaken regarding the version of LabVIEW that comes with development suite. You are correct that 2010 SP1 is the version included with 2011 (my apologies). Regarding why it is asking for those items, I found out that the build is actually looking for the LabVIEW Run Time installer executable file. When LabVIEW installs, it references the installer executables from the directory that the setup was run from. If you ran the LabVIEW installer from a disc, it would be looking for the Run-Time engine installer (setup.exe) from the LabVIEW installer disc. It could be possible that when you installed LabVIEW DS 2011, the configuration did not add the run time installer if you did a customized installation. You can install the Run Time Engine from the link in my previous post that will allow LabVIEW to have access to the Run Time Engine installer. I'd also suggest for that you copy the LabVIEW Run Time Engine installer (the setup.exe in the root folder of the installation media) to a static location if you anticipate needing to reference it for other builds. 


Regards

Doug W

Applications Engineer
National Instruments
0 Kudos
Message 15 of 15
(373 Views)