creating exe file

[Mrtechie]

Hello all, 

I have a created an exe for my project. In that two boxes are there on the right side . 1 ) start up Vi's   2 ) always included . In start up vi's we need to add the main opening VI. I have a doubt about the moving Vi's to the

Always included.   shall I need to add even a CTL files, global variable.vi  also huh? 

any material or links ?

[Blokk]

Usually you only need to add VIs to the "Always included" field, if you call these VIs dynamically. Besides, normally you do not need to add controls and global variables to this field, your VIs referencing them implicitly.

So in most cases, you just leave this field empty. There are other cases when you need to include files here (like separate run-time menu files, help files, etc.)...

Check these resources out:

https://www.ni.com/en/support/documentation/supplemental/19/introduction-to-the-labview-application-... 

https://www.ni.com/docs/en-US/bundle/labview/page/developing-and-distributing-an-application.html

here is the help for LV2017: http://zone.ni.com/reference/en-XX/help/371361P-01/lvhowto/develop_distribute_applications/ 

[PalanivelThiruvenkadam]

Include Dynamically Calling VI's in Always Included, 

[Bob_Schor]

As I am sure the references in Blokk's response make clear, many LabVIEW Projects need nothing more than the Top Level VI to be chosen as the Start Up VI.  This is because in most cases, the Application Builder can find the names of all of the sub-VIs it needs simply by looking at your code.

A sensible thing to do is to simply try to build an Application (.exe) from the Project.  See if there are errors during the Build, then see if it runs from without error when you call the Executable (on the same PC as the Development machine).

Whenever possible, I try to use Static VI References if I need to call a VI "by reference" (such as Start Asynchronous Call), as this type of call will also "auto-resolve" using just the single Start Up VI.

Bob Schor