This is my setup:Windows 2000
LabVIEW 8.5 Full Development System +Application Builder
This is the problem... 1. Start a new project, add one vi to it and one batch file (test.bat).
2. Create an Application build specification using the one vi as startup and the .bat file as always included source file.
3. Build the application
4. Create an Installer build specification adding the executable (and all it's associated files) compiled in step 2.
5. In the 'Advanced' category check the 'Run executable after installation' checkbox and select the .bat file to be executed, click OK.
6. Click OK on the Installer build specification window to close it.
7. Reopen the Installer build specification and navigate back to the 'Advanced' category.
The 'Run executable after installation' checkbox is unchecked and the field is blank!!!If this Installer is built, the batch file does not run. (of course it doesn't... LabVIEW unchecked the box!)
Have I missed something? Does this work for anyone else? Is there a bug with my setup or is there a bug in LabVIEW 8.5 Application Builder.
It worked in 8.2.1. Then some crazy stuff started happening when I ran installers made in 8.5 with projects whose installers were initially defined in 8.2.1.
For some reason these projects retain the 'run executable after installation' setting, but they smeg up the execution!
After the install completes, it tries to run
something, but just throws up a bunch of error prompts stating that folders don't exist.
It also runs other accessory exes that I included in the distribution.
There are other problems with the application builder but I think this post is long enough.
Does anyone have any suggestions?
Troy - CLD
"If a hammer is the only tool you have, everything starts to look like a nail." ~ Maslow/Kaplan - Law of the instrument
