Hi GuysPaddling with my head above 'lurksville' to ask of the wise onesI have two relatively large and complex LabVIEW source code applications that we use internally with equips and sensors etc.I just upgraded both of these applications to 8.5.1 from 8.2.1. Hopefully you still have a backup in the previous version. Hi GuysPaddling with my head above 'lurksville' to ask of the wise onesI have two relatively large and complex LabVIEW source code applications that we use internally with equips and sensors etc.I just upgraded both of these applications to 8.5.1 from 8.2.1. We have a pretty big app, and we build it frequently without crashing LV.

This is very heavy to do, but most economical as buying the option 'Application builder', proportionnaly with the cost of the runtime engine 'Labview Home Edition'. In revanche,this licence 'Home edition ', is an interesting version to learn Labview, during lot of time. Thanks in advance for those here which helped me. 如下四个serial Number 可以先不输入，而使用试用版软件：LabVIEW 2016,Application Builder for LabVIEW2016,Report Generation Toolkit for LabVIEW2016,Database Toolkit for LabVIEW 2016，直接点击Next；.

I would just use a divide and conquer approach. Take the top-level VI and delete half of the subvis, patch up the loose wires, and build it. If it doesn't crash, delete the other half of the VIs and see how that goes. Naturally you will want to try eliminating all calls to various features like VISA, GOOP (if possible), et cetera. It sounds tedious, and it is, but in one afternoon you should be able to finger the culprit.

Then NI Tech support should be able to help you if the fix is not obvious at that point.Good luck! First fix:Place any dynamically called VI inside a Strict VI reference, this will force the builder to include the dynamic VIs inside the executable.One question, were you able to build the executable inside 8.2?TonSorry, was away for a day or two. Actually I never tried the full executable in 8.2 but I do remember having better luck with portions of it.I've read all the responses (Thx btw, u guys always impress with the level of expertise ) and I am thinking for now at least I should look mainly into the GIT toolkit as the most likely cause of severe problems as in not even seeing error dialogs yet.I would guess dynamically called VI's without strict references would be the second suspect.The divide and conquer approach is probably where I'll start. I am used to getting away with LV 7.1 where everything at least gave an error. It was tedious but at least there was an endpoint. We really do not need to make executables out of these programs for long time yet so I have option of looking into it a little at a time.Ive got a number of GIT 3.05 classes made and it makes sense to me to start there, maybe try to remove dependenciesand encapsulate them a little better and try to make some executables out of them piecemeal first.Boy I wish I had been keeping up with this when developing these two beasts. Hehe.Might take awhile But I'll report my progress as it goes.Thx again:beer.

LabVIEW 2013 and 2014In LabVIEW 2013, application builder enhancements were added so that LabVIEW automatically selects installers for the drivers and other software components required by the built application. The user may still choose to add NI installers, just as explained in 8.x versions below. Unlike earlier versions, you must remove the checkmark from the Automatically select recommended installers checkbox on the Additional Installers page of the Installer Properties dialog box for your installer.

When the checkbox is disabled, the Run-Time Engine should still be selected. Other drivers will then be available to include. Like LabVIEW 8.6 to 2012, the Installer source location field is not editable. Information about changes to application builder in LabVIEW 2013 is linked below.LabVIEW 8.6 to 2012In LabVIEW 8.6 and later, you can include other NI installers, just as explained for the other 8.x versions below. Unlike the other 8.x versions, LabVIEW 8.6 and later do not offer an editable Installer source location field. Sin on loresca.

Select the desired installers to bundle with the LabVIEW application installer.LabVIEW requires the additional installer’s source MSI and.id files that were used for installation on the development machine to be able to install the additional installer on other machines. These source files are not usually left on the development machine after installation. The Installer source location field tells LabVIEW where to find these needed source files. LabVIEW will, by default, set this field to the last location used to install the additional installer on the development machine.

If you installed your additional installer from a CD, you will need to put that CD into your drive before building your installer. If you downloaded the additional installer from ni.com/support and deleted the source, you will need to download the same version and unzip it again before you build and point the Installer source location field to this new folder. If you installed from a network location, you will need to still have access the files on the network drive or one of the two above options.If LabVIEW cannot find the needed files, it will throw up a distribution error asking for the correct source distribution location. Refer to the linked for more information.You can also include other non-NI installers in LabVIEW 8.x.

This requires using the executable method that is described below.For more information on building LabVIEW application installers, see the related links section below.LabVIEW 7.1 and earlierIn previous versions of LabVIEW, the LabVIEW installer options give you the ability to launch an executable after the installation (refer to linked below). The problem with launching an executable in this fashion (in LabVIEW 7.1 and below) is that you can only launch a single executable and that executable must be included as a support file in the installer. Additional InformationIf you need to include the LabVIEW Development Environment, 3rd party installers, and other installers not included in the Additional Installers list, read about the options in.Some runtime driver (eg. NI-DAQmx Runtime) may not be found in the Additional Installers page of the Installer Properties dialog box.This is because they are now bundled and selectable within the full installer.Please refer to the solution in Downloading 19.0 NI-DAQmx or NI-VISA Driver Runtime Engines to install the required runtime driver.