05-25-2009 10:20 AM
You may use commandline options. If you use the run option in windows it may look like this.
"C:\installer\Volume\setup.exe" /l*v c:\Package.log
This will create a log in c:\ named package.log
05-26-2009 12:12 AM
Parag D wrote:
Well, I believe that LabVIEW Application Installer cannot be created through Installshield.
It can be created using Install Shield. In one of my projects, we used it to offer wider options to the customer for the distribution of various files & folders in a single package. It was during my days with LV 7.0 & 7.1.
If you have somebody who uses a text-based prog language in your company, please ask them. They may be in a better position to guide you with more details of it.
05-26-2009 12:21 AM - edited 05-26-2009 12:23 AM
05-26-2009 12:41 AM
05-26-2009 10:46 AM
Hi Parag,
I would not recommend trying to build the installer using InstallShield, as it will not be able to pull in any of the NI drivers, LV run-time engine, or support components.
While the Microsoft Installer engine (MSI) does not have explicit support for doing this, Coq's suggestion above is a good one. Specifically, you can:
Regards,
- WesW / NI
05-26-2009 11:16 PM
Coq's suggestion worked and now I am able to monitor the files installed!
Thanks all!