Deployment vs Application builder

Question

Hi there, I just need a little help getting something straight in my head.
I've been developing a test-sequence-program on my PC here, which will sooner or later be put into the factory. We don't really want a labview licence sitting out in the factory, so I'm looking at my options regarding building standalone executables. I'd be very appreciative for any help with the following questions:
a) Deployment vs Application Building - what is the difference? I have the Labview 8.2 Full Version, and would prefer to avoid buying a separate application builder if the Full Version does the trick already.
b) Say I have some controls on the front panel (eg. "maximum voltage allowed"), which I want to set on startup - I don't want the people using the tester to be able to change this afterwards though.. is it possible to add command line switches?
eg. myprogram.exe -maxvoltage 20
Thanks in advance.

Answer 1

If you want to run your application on a computer that does not have LabVIEW installed, you need to create a standalone application using the application builder. The application builder is not included in LabVIEW full (only professional and higher), so you would need to purchase this seperately.
Yes, it is possible to add commandline switches. In the application builder, you should specify to pass all parameters to the application. In your code you can read the commandline parameters and do whatever you want with that information.
From the online help:
Pass all command line arguments to application—Passes all arguments as user-defined arguments to the application when you launch it from the command line. If you remove the checkmark from this checkbox, only the arguments after two hyphens (--) in the command line pass to the application as user-defined arguments. Use the Application:Command Line Arguments property to read the user-defined command-line arguments passed when the application launches.
LabVIEW Champion . Do more with less code and in less time .