NI TestStand
Can we make ".exe" file of ".seq" file for distrubution?
Hi,
The only exe that exist is the operator interface. (unless of course that your steps call exe's).
Therefore, you could bundle all your sequence files, VIs and SupportVIs, DLL's etc when you create your Operator Interface exe and installation using your Labview Application Builder.
But this is not such a good idea, as it's possible you could have sequence files etc that you what to install as new versions or updates but your operator interface never changes therefore you dont what to have to uninstall the operator interface to restall again with your new sequence file etc.
What I have used to good effect, is in the \labview\projects\ is the old install library ( call oldinstall.llb). This contains the old Install Create Distribution Kit.vi (this is from th
e days when the application builder was two seperate tasks - builder the exe and create the distribution kit). This allows you to create just the distribution kit without having to build an exe. Also this installation kit doesnt require you to be an administrator when installing on an NT system.
Alternatively you could use a 3rd party Installation package such as InstallShield.
Hope this helps
Regards
Ray Farmer
The only exe that exist is the operator interface. (unless of course that your steps call exe's).
Therefore, you could bundle all your sequence files, VIs and SupportVIs, DLL's etc when you create your Operator Interface exe and installation using your Labview Application Builder.
But this is not such a good idea, as it's possible you could have sequence files etc that you what to install as new versions or updates but your operator interface never changes therefore you dont what to have to uninstall the operator interface to restall again with your new sequence file etc.
What I have used to good effect, is in the \labview\projects\ is the old install library ( call oldinstall.llb). This contains the old Install Create Distribution Kit.vi (this is from th
e days when the application builder was two seperate tasks - builder the exe and create the distribution kit). This allows you to create just the distribution kit without having to build an exe. Also this installation kit doesnt require you to be an administrator when installing on an NT system.
Alternatively you could use a 3rd party Installation package such as InstallShield.
Hope this helps
Regards
Ray Farmer
