Can LabVIEW Application Builder build just an installer for existing executables without building a new executable?

[aka47]

I have several executables I have built with the LabVIEW Application Builder. For reasons of my own, I need to build them separate from the install. However, I cannot find a way to generate a .bld file that will just make an installer without generating a new executable. So I tried creating a dummy.exe with just support files for the installation and no VIs in it. That works ok, but application builder always wants to create a program item for dummy.exe. Even when I uncheck the Create program item box and resave the .bld file, the next time I load the .bld file, the box is checked again.

[nicola]

I'm not sure the right idea, but you can try to save two .bld file, one just for the exe file and another with the installer cheked.
Maybe you can build a dll and aim at the exe file by the files option in the installer settings (uncheck the lybrary and check the exe).This method build a dll of the vi and point an existing executable.
Best regards Nicola

[modicon]

aka47 wrote in message news:<506500000008000000CD9B0000-1042324653000@exchange.ni.com>...
> Can LabVIEW Application Builder build just an installer for existing
> executables without building a new executable?
>
> I have several executables I have built with the LabVIEW Application
> Builder. For reasons of my own, I need to build them separate from
> the install. However, I cannot find a way to generate a .bld file
> that will just make an installer without generating a new executable.
> So I tried creating a dummy.exe with just support files for the
> installation and no VIs in it. That works ok, but application builder
> always wants to create a program item for dummy.exe. Even when I
> uncheck the Create program item box and resave the .bld fil
e, the next
> time I load the .bld file, the box is checked again.

The easiest is to download the self-extracting Run-Time engine from
the NI Website:
http://digital.ni.com/softlib.nsf/websearch/452C309469E56DEB86256D2B004F2396?opendocument
into whatever location you are gonna park your executables. This will
set up all the dll stuff, including the browser plug-in, that the
..exe's need. The addy given is for the 7.0 runtime; if your .exe's
are 6.1 or earlier you will need a different engine. In any case, the
exe's should just work. I did this exact process this very morning,
part of my own upgrade to 7.0...