Forced RT executable shutdown when installing a second RT executable?

[Synap]

I am running multiple RT executables on a windows server.  Whenever I install a new revision of one of them, I must shut them ALL down to complete the installation.  I'm sure this is because they are all dependant on the Real Time engine (or something similar). 

Is there a way to build the executables so they all run their own copy of the RT engine so this depandancy is no longer a problem?

[Chris_Cilino]

Synap,

I think I get the main idea of your question. You have a LabVIEW installer (executable + run time engine (RTE)) that you want to install while other exes are using that run time engine. However, when you try to run your installer, you have to shut down all of your exes using the RTE. Something you could try is not including the RTE in the installer. In effect, you'll only be copying an exe to the computer and the RTE isn't even touched. So the problem should be solved by leaving out the RTE. Post to let us know if that works out for you. Thanks!

Best Regards

Chris C

National Instruments

Applications Engineering

[Synap]

It did work!

For those who find this thread in the future, achieving this is as easy as going to the "Installer Settings" tab on the app builder, clicking the "Advanced" button, and unchecking "LabView Run time Engine".  When the program is installed, it will use the RT Engine already on the machine, so don't mix application builds with different LabView revisions if you do this!

Thanks Chris_C!  You've saved me hours of time!

[Chris_Cilino]

Any time Synap! Always glad to help.

Chris C