12-31-2009 07:29 PM - edited 12-31-2009 07:29 PM
Solved! Go to Solution.
01-01-2010 03:32 AM
01-04-2010 12:26 AM
if you look in to the "Setup.ini" file under the section "[Distribution]" there is a item called "Version" and that tells you which is the current installer version.
Guru
01-04-2010 04:59 PM
Hi pRoFiT,
In addition to the information provided by Guru, you can run the LV install from the command line with the options mentioned in the following Knowledgebase:
What Are the Options With a Command Line Install for the LabVIEW Run-Time Engine for Windows?
http://forums.ni.com/ni/board/message?board.id=170&message.id=465495#M465495
This is also a handy resource for manipulating installers and executables:
Creating a Batch File
http://digital.ni.com/public.nsf/allkb/B2640E34C4654F7B86256D07006D843D?OpenDocument
Best Regards,
~Nate
01-05-2010 05:46 PM
01-05-2010 06:00 PM - edited 01-05-2010 06:00 PM
Nate,
Your first link is the link to this thread? Is there another link?
Creating a batch file is kinda what i had to do. Sorta. 😉
The Solution:
So i figured out one way to do this. I will try to add PNG snippets of what i did.
First off i know how to get the version from a file using .net calls. So one PNG snippet is that process.
Then i needed to figure out how to get the exe file out of the installer folder without installing everything. I tried building the cabinet.dll CAB commands into labview but got stuck after an hour. My next way was the cheating way but it works. I use windows EXPAND.exe command line program and send it the path to the CAB file that has the exe i need to look at. I then run FileVersionInfo on the EXE and delete the file.
My assumption so far is that the installer will make a /bin/dp/data.cab file and the main EXE will be in there named somthing.EXE.something so *.EXE.* is what i extract. If there are multiple EXE files then i will need to rethink my subvi. For now most of our applications are single EXE files.
Maybe this will be helpfull to someone else? maybe not.
01-06-2010 09:40 AM
Oops,
I think I meant to put something along these lines:
Automating the Installation of a Single Installer
http://digital.ni.com/public.nsf/allkb/878FC4C374013ADF8625733D00688F67?OpenDocument
I can't find the KB I was going to link yesterday. Anyway, this one contains some of the same setup commands, and I'm glad that you got it figured out for your specific case!
~Nate
01-06-2010 01:13 PM
Nate,
Thanks. I may use the silent installation with progress part. Will make my tool simpler. This way i can update and install apps without needing input from users.
-pRoFiT aka Corey S.
03-01-2010 05:19 AM
03-02-2010 05:41 PM