LabVIEW 2010 App Builder/Installer- Target OS Options

I will shortly be migrating from LV8.6.1 Devloper Suite in Win XP 32 bit to 2010 running in Win7 64 bit.
Does the applicationbuilder and installer have the option to deploy Win XP 32 bit applications along with the corresponding run time engine?
Thanks
-AK2DM
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
Solved!
Go to Solution.

Hmmm, do you have a time machine?
LabVIEW 2011 is not released yet. You'll have to wait until August for that.
There is no specific Windows XP selection in the setup section of the Application Builder. It will simply create an installer for whatever Windows platform you are running at that moment. So if you run LabVIEW 32 Bit it will create a LabVIEW 32 Bit application and installer and if you run LabVIEW 64 Bit it will create an according application and installer. Needless to say that 64 Bit application and installer can only run on a 64 Bit system, while you can install the 32 bit application on either system.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Similar Messages

LabVIEW 2010 App Builder: Registry editor has issue with keys of the same name at the same level in registry tree

This is a bug report for an NI application engineer. Please file a CAR.
In a LabVIEW 2010 project, create a new installer build and go to the Registry editor.
Enter some keys like the following
Click OK to close the installer wizard.
Now reopen the build specification and go to the Registry editor. The registry editor comes up blank and non functional.
I believe the registry entries are still written when the installer executes, but you cannot edit the registry any further in LabVIEW 2010. This was not an issue in LV 2009. The issue seems to stem from having two keys with the same name at the same level in the registry tree (in this case, the two "Test" keys).

Hi sensor_daniel,
This was reported to R&D (#305026) for further investigation.
Thanks for the feedback!
Have a great day,
Chris V
Applications Engineer
National Instruments

USB/Serial Drivers and App Builder Installer Questions...are drivers included in the Installer with the LV runtime engine?

Hello all,
I'm wondering if someone can help me out with how drivers and all are treated with applications distributed with App Builder, used to create a stand alone, full install of app and labview engine with Installer.
What has happened is, my application was created using the NI branded USB to RS232...and USB to RS485, and they work great.
On the application when running..you fire it up, it finds the USB to serial device, and I have a dropdown that finds the available COM ports to use (along with setting parity, etc).
I've installed on different computers (without previous labview installs) with the installer. They all worked.
The customer has received the installer....and despite us telling them to use the NI branded USB/Serial interfaces..they are trying to work with a different USB/serial cable.
They say the COM ports aren't even showing up when they run the installed application.
So, I'm not sure where to start. Is this a driver issue? Does the App Builder Installer...install the drivers for the interfaces I was using with it? Is there a way for the person to find and install a driver on their own...or would I have to somehow find out a driver for what they use....then, basically redo the App Builder Installer build...to include that driver with the executable I send back out?
I guess I basically need a better understanding of how drivers for external access/communications are handled when you use App Builder to create a stand alone application complete with the labview runtime engine...and nothing else.
Thank you in advance,
cayenne

The main thing is that LV uses VISA to talk to serial port whether native on the machine or from USB dongles that you plug into the computer. It sounds to me like their dongles aren't working.
Can the customer see the ports in the Windows Device Manager? Can they access them through something like hyperterminal? How does your program find the USB/Serial devices?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

LV 8.0 App Builder - Installer including NI-VISA

Hallo,
how can I include Ni VISA into the installer files with the LV 8.0 App
Builder for using Visa functions?
Kind regards
Niko

Hi Niko,
Matt's right on the money here. You can check out these links if you need more detail:
http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
http://zone.ni.com/reference/en-XX/help/371361B-01/lvdialog/addl_install_info_db/
Let us know if you have questions!
Charlie S.
Visit ni.com/gettingstarted for step-by-step help in setting up your system

Labview 8 app builder file placement

I'm trying to build an installer (I sure wish I could just use install shield) for an application. I'm trying to have files copied to c:\<directory> but that doesn't appear to be an option. Under the Source Files selection, on the right side (destination) the only directories that appear are:
[DesktopFolder]
[LV80RTEDIR]
[LVDIR]
[PersonalFolder]
[ProgramFilesFolder]
[SystemFolder]
[TempFolder]
[WindowsFolder]
[WindowsVolume]
Also, when it asks the user to select the directory to install files, is there a way to hide the part for installing the National Instruments files? I'd like that just to be default where the user cannot change it, but not show it as well.

The destination "[WindowsVolume]" corresponds to whatever volume in which Windows is installed, which is the C:\ drive on most systems. The reason why the installer doesn't allow you to specify C:\ explicitly is because that drive may not exist on the target PC or it may correspond to a removeable storage drive, like a CD-ROM. By specifying the windows volume instead, you ensure that you are always installing to valid location.
As for your second question, I'm not sure what you mean by "the National Instruments files". Are you talking about the LabVIEW Run-Time Engine and NI drivers? If so, you can run a batch file after your installer completes (set up under the "Advanced" tab) that installs any installers silently instead of bundling those installers with the installer for your executable. You can then use command line arguments to specify varying levels of silence while your other installers install. The online Knowledgebase here explains the process in detail.
Kind Regards,
E. Sulzer
Applications Engineer
National Instruments

LabVIEW 2011SP1 Error building installer: LabVIEW Run-Time Engine 2013 is missing 3 dependencies???

I'm having a problem building an installer in LabVIEW 2011SP1.
It's been a while since I've tried to build an installer but it used to work fine and building executables is still working fine.
Now when I try to build the installer I get "The build was unsuccessful."
Possible reasons: Error generating preview for My Application 3.1.7.
Details:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_InitializeDistribution.vi >> IB_MSI.lvclass:Report_Preview_Error.vi >> IB_Source_Container.lvclass:Report_Preview_Error.vi
Loading product deployment information
*** WARNING ***
NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing. Visit ni.com/info and enter the Info Code "" for more information.
*** Error: An internal error occurred for which the cause is unknown. (Error code -41)
*** Error Details:
Error in MDF API function: _MDFCommon_GetNextLogMessage
Error in MDF::GetInstance - MDF static instance is not initialized!
*** End Error Report
Loading product deployment information
*** WARNING ***
NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing. Visit ni.com/info and enter the Info Code "" for more information.
The really strange thing about this is that I'm using LabVIEW 2011SP1, I don't even have LabVIEW 2013 installed, not even the runtime.
Where is the problem? Why is it even complaining about LabVIEW 2013? Has anyone seen this before?
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle
Solved!
Go to Solution.

I do have the LabVIEW 2013 discs but didn't install it.
I checked in Control Panel > Programs and Features > National Instruments Software and the LabVIEW 2013 Run-Time is not listed there.
I also checked in MAX > Software and I must have missed it the first time I looked. LabVIEW Run-Time 2013 is listed there after all.
Now I remember installing VISA 5.4 to get rid of a nasty bug. It must have installed the 2013 Run-Time when I did that.
So now I need to distribute 2 runtimes with my application?!?!
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle

App Builder Installer Build Registry Keys no longer created in Vista.

This board has been a great resource for answers...thank you all for your help.
Last week (7/31/09), an automatic MS Windows Vista Home Premium
upgrade was performed on my development PC. After the upgrade, I
used AppBuilder to build the final version of my application, which writes
3 string keys to the Window's registry. The Installer build completed successfully,
however, when I run setup.exe, I received an OS error stating that I don't
have permission to update the registry. I have full admin rights AND
User Account Control (UCS) is OFF. This error notification occurred 3
times, once for each registry addition attempt.
The installation was working correctly prior to this Vista update and still works in XP.
Any help would be greatly appreciated!
Please note that this is VI independent- the registry keys were created through
the AppBuilder 'Installer' tool.
I worry that this problem will manifest itself with all new LV application installations
that have the Vista upgrade.

Does the installation fail only when you try to install on computers that have the Vista update? Or since you have updated your development computer, when you build the installer again the installation will fail on any computer? Have you tried installing it on more than one computer with the Vista update?
Please attach the installer log for when the installation fails.
http://digital.ni.com/public.nsf/allkb/AB597E885DB7D16B86256E92006DB232?OpenDocument
Cheers,
David Goldberg
National Instruments
Software R&D

Impossible de télécharger la dernière version du DPS Apps Builder- fichier d'installation endommagé

Bonjour,
J'essaye sans succès depuis hier de télécharger la dernière version du DPS
Apps Builder depuis votre site ou via le support en ligne et à chaque fois
que j'essaye de l'ouvrir il me met le message :
Désolé, une erreur s'est produite.
L'application n'a pas pu être installée, car le fichier d'installation est
endommagé. Essayez d'obtenir un nouveau fichier d'installation auprès de
l'éditeur de l'application.
J'ai réessayé 20 fois.
Je suis sous Max OS X (version 10.6.8)
JE CRAQUE !!!
Help me
-- Sophie JOSSE

DPS App Builder installer file is damaged

Building App Gives Error 6 about 50 - 80 - 99% of the time. Windows7, LabVIEW 2010 SP1

Hi
First off here is a link to a discussion of the problem. http://forums.ni.com/t5/LabVIEW/Error-6-occurred-when-building-an-Executable-in-Labview-2009/m-p/997...
I have tried all the suggestions on this link with no luck.
Background: have been using LabVIEW 2010 without problems since Sept, then I started getting the error 6 with the following message.
" Error 6 occurred at Delete in AB_Engine_Delete_Internal_Files.vi->AB_EXE.lvclass:Build.vi
->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller "
This started on one project and is now occurring on another project. Sometimes it builds 50% of the time, other times I can't get it to build at all. I have upgraded to SP1, no change.
Here are some things I have tried.
Moved build directory to c:\a
Renamed project, moved project right under c:\
Disabled Google , disabled Win indexing, disabled Win7 user acct. Control, run LabVIEW as Admit all the time, win explorer closed
mass compiling, closing the project, closing LabVIEW, re-booting
Unistalled LabVIEW 2010 SP1 and re-install, twice.
I believe I rebuilt my project in a new project.
I moved my projects to a WinXP system laptop I have, and they never get Error 6 ! Short term fix, but I have to use Win7. So I hope this means it is not my code.
The funny thing is that this is totally random. The unfunny thing is having to explain to a client I can't get my code to compile during a frustrating 95% of the time failure episode, yikes!
Any help and suggestions would be welcome.
BTW, the next step is to totally uninstall LabVIEW with a 'special' procedure and piece of code sent to me. Don't want to, but am really at wits end. Also waiting to hear back from my service ticket, but am desperate to have parallel solutions to try.
Thanks
Mark Ramsdale

Thanks for the clarify.
I also meant to post this link. It has a lot of info, this is the link I tried most if not all of the suggestions for.
http://forums.ni.com/t5/LabVIEW/Get-Error-6-about-50-of-time-when-building-Application/td-p/1242634
By the way, I was told that uninstalling LabVIEW will not resolve the issue, dodged a time killer :-)
It seems the error is caused by Win7 and file reserving. Waiting to hear back on that. Have an SR.
Again, any suggestions welcomed, maybe some Win7 ideas from those who know more about it.
mr
Mark Ramsdale

Media size option in LV app builder 6.1?

Where is the media size option in app builder for LabView 6.1? I want to create small .cab files that can be place on diskette if needed. It's no longer on the Installer Settings tab. What am I missing here?

The last time I built an executable with an installer, it broke it up into multiple installer files, each one suitable for storage on a 1.4M floppy.
In any case, one thing you could do is put the installer files in a Zip archive and then have the zip program you're using split the archive into smaller files that you can later rejoin. I just checked and WinZip 8.1 will generate split segments as small as 64K.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Error 1 when building my application in Labview 2010 Version 10.0f2

I am getting the following error trying to build my application in Labview 2010 Version 10.0f2 and I get the following error:
Error 1 occurred at Invoke Node in AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
Method Name: Linker:Write Info To File
I have searched and can find no real sollutions to this problem. I did the updates and still nothing. Now I can't even build an app with Laview 8.6. I reference several .NET items and refuse to rebuild each and every one of them. My only option at this point is to uninstall all Labview and then reinstall 8.6 so I can do something.
Help if you can.

Hello RBrown
I am really sorry for this inconvenience! This is a known issue.
Can you please attempt the following for me:
When you are building an application, under Advanced please check the last box "Use LabVIEW 8.x file layout"
If that doesn't work, you may need to rebuild the LLB in a separate directory with new names, and use it as the build inclusion.
Here are some forum posts strictly for your information:
I have found users that have had similar issues. I am trying to make this workaround work for you.
http://forums.ni.com/t5/LabVIEW/error-1052/m-p/912192
This is a known issue that some customers have already commented on:
http://forums.ni.com/t5/LabVIEW/NI-Please-don-t-put-illegal-vi-names-in-your-toolkits-thanks/m-p/745...
I have filed a corrective action for this issue and I will add you to the list of individuals who need this issue resolved.
Sincerely,
Greg S.

Problems with Installer LabVIEW 2010 SP1

Hi,
I am trying to build an installer for an .exe using the project tool. I can build the .exe, but I get the following error message when I try to build the installer:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi
Loading product deployment informationAdding files to installerDone adding filesPreparing to build deploymentCopying products from distributionsCopying distribution 'NI-Serial 3.7' from: C:\National Instruments Downloads\NI-Serial\3.7.0\ to: D:\workspace\swarm\trunk\LabVIEW\builds\SWARM Analysis Viewer v1.0.1\SWARM Analysis Viewer v1.0.1 Application Installer\Copying distribution 'sapphire_sw_packet_reader' from: D:\workspace\Sapphire GSE\LabView\LabVIEW 2009\source\builds\sapphire_sw_packet_reader\Sapphire Sub Window Packet Reader Installer\Volume\ to: D:\workspace\swarm\trunk\LabVIEW\builds\SWARM Analysis Viewer v1.0.1\SWARM Analysis Viewer v1.0.1 Application Installer\Building deploymentCopying setup filesSetting merged database informationSetting product informationSetting developer part informationStarting final buildValidating... ***************** Error: An internal tool or library returned an error. (Error code -21)Error MessagesInput directory 'C:\National Instruments Downloads\NI-Serial\3.7.0\Products\MDFSupport\MDF' not found for part 'MDFSupport.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\MDF Support {1814BD68-741C-429B-9EA7-C6D1385777C8}.xml'.Input directory 'C:\National Instruments Downloads\NI-Serial\3.7.0\Products\MDFSupport\MDF' not found for part 'EulaDepot.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\MDF Support {1814BD68-741C-429B-9EA7-C6D1385777C8}.xml'.Input directory 'D:\workspace\Sapphire GSE\LabView\LabVIEW 2009\source\builds\sapphire_sw_packet_reader\Sapphire Sub Window Packet Reader Installer\Volume\Products\LabVIEW_Web_Server_RTE_2010\LVRTEWebServer' not found for part 'NIWebServer_LVRTE.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI LabVIEW 2010 Run-Time Engine Web Server {DB68B420-5382-48EE-9A2A-CB984FEBB192}.xml'.Input directory 'D:\workspace\Sapphire GSE\LabView\LabVIEW 2009\source\builds\sapphire_sw_packet_reader\Sapphire Sub Window Packet Reader Installer\Volume\Products\LabVIEW_RT_NBFIFO_2010\LVRT_NBFifo' not found for part 'LVRT_NBFifo_2010.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI LabVIEW 2010 Real-Time NBFifo {2BC9B2CE-D569-4ADC-A8A0-170F2FD57139}.xml'.Input directory 'D:\workspace\Sapphire GSE\LabView\LabVIEW 2009\source\builds\sapphire_sw_packet_reader\Sapphire Sub Window Packet Reader Installer\Volume\Products\LabVIEW_SysStatePublisher_2010' not found for part 'NI_SysStatePub.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI System State Publisher {19F59734-0740-49E6-818D-53C1CA6B4ABE}.xml'.Input directory 'D:\workspace\Sapphire GSE\LabView\LabVIEW 2009\source\builds\sapphire_sw_packet_reader\Sapphire Sub Window Packet Reader Installer\Volume\Products\LabVIEW_SysStatePublisher_2010' not found for part 'NI_SysStatePub64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI System State Publisher {19F59734-0740-49E6-818D-53C1CA6B4ABE}.xml'.
***************** Error Details:Error in MDF API function: _MDFBuildDist_BuildError List.\InputParser.cpp(255): IInstallerError 120Input directory 'C:\National Instruments Downloads\NI-Serial\3.7.0\Products\MDFSupport\MDF' not found for part 'MDFSupport.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\MDF Support {1814BD68-741C-429B-9EA7-C6D1385777C8}.xml'.While validating input parts.
.\InputParser.cpp(255): IInstallerError 120Input directory 'C:\National Instruments Downloads\NI-Serial\3.7.0\Products\MDFSupport\MDF' not found for part 'EulaDepot.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\MDF Support {1814BD68-741C-429B-9EA7-C6D1385777C8}.xml'.While validating input parts.
.\InputParser.cpp(255): IInstallerError 120Input directory 'D:\workspace\Sapphire GSE\LabView\LabVIEW 2009\source\builds\sapphire_sw_packet_reader\Sapphire Sub Window Packet Reader Installer\Volume\Products\LabVIEW_Web_Server_RTE_2010\LVRTEWebServer' not found for part 'NIWebServer_LVRTE.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI LabVIEW 2010 Run-Time Engine Web Server {DB68B420-5382-48EE-9A2A-CB984FEBB192}.xml'.While validating input parts.
.\InputParser.cpp(255): IInstallerError 120Input directory 'D:\workspace\Sapphire GSE\LabView\LabVIEW 2009\source\builds\sapphire_sw_packet_reader\Sapphire Sub Window Packet Reader Installer\Volume\Products\LabVIEW_RT_NBFIFO_2010\LVRT_NBFifo' not found for part 'LVRT_NBFifo_2010.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI LabVIEW 2010 Real-Time NBFifo {2BC9B2CE-D569-4ADC-A8A0-170F2FD57139}.xml'.While validating input parts.
.\InputParser.cpp(255): IInstallerError 120Input directory 'D:\workspace\Sapphire GSE\LabView\LabVIEW 2009\source\builds\sapphire_sw_packet_reader\Sapphire Sub Window Packet Reader Installer\Volume\Products\LabVIEW_SysStatePublisher_2010' not found for part 'NI_SysStatePub.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI System State Publisher {19F59734-0740-49E6-818D-53C1CA6B4ABE}.xml'.While validating input parts.
.\InputParser.cpp(255): IInstallerError 120Input directory 'D:\workspace\Sapphire GSE\LabView\LabVIEW 2009\source\builds\sapphire_sw_packet_reader\Sapphire Sub Window Packet Reader Installer\Volume\Products\LabVIEW_SysStatePublisher_2010' not found for part 'NI_SysStatePub64.msi' in product 'C:\Program Files\National Instruments\Shared\MDF\Manifests\NI System State Publisher {19F59734-0740-49E6-818D-53C1CA6B4ABE}.xml'.While validating input parts.
*** End Error Report************** Done building deployment
Any ideas?
Thanks.
Bob

CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_Build.vi >> NI_MDF.lvlib:MDFBuildDist_Build.vi Loading product deployment information Adding files to installer Done adding files Preparing to build deployment Copying products from distributions Building deployment Copying setup files Setting merged database information Setting product information Setting developer part information Starting final build Validating... Copying files... Updating files... Creating merged database... ************** *** Error: Windows SDK function returned an error. (Error code -12) ************** *** Error Details: Error in MDF API function: _MDFBuildDist_Build ERROR: Caught Windows Error: The operation completed successfully. Unable to CreateFile for MSI ReadStream target file *** End Error Report ************** Done building deployment
I have same errors, plz see above, can anyone help?
MJ

How do I create a single file installer for LV 6.1 App Builder Output?

I have created an application using the 6.1 App builder and it installs fine. To be able to send this app to others, I would really like to put it in something like a self extracting executable file. How can I do this with app builder or can you suggest another software to buy that will let me create this.
Thanks for any help that you can provide

You raise a number of important points. I'll answer to the best of my knowledge.
1. Usually true. Win98/2K/XP have the Windows Installer Service built in, but 95/98/ME require InstMsiA.exe, and WinNT4 requires InstMsiW.exe. The difference is in the character set (ASCII vs. Unicode), and I don't know how that difference applies to the non-Roman alphabet installations. It's safest to include both if you're going to include one.
On the same subject, I noticed that the first thing the LV7 evaluation installer does on a Win2K box (and therefore probably on a Win98 box as well) is update the Windows Installer service, so LV7-built executables may very well require InstMsiA.exe/InstMsiW.exe on Win98/2K.
2. I think so. I usually don't distribu
te LabVIEW EXEs as self-extracting installers, but it probably is safest to wait until the setup is complete before returning control to the self-extractor software.
3. True. (And note that one of the circumstances under which you might repair/update msiexec is with LV7 on Win98/2K).
4. True. Setup.exe appears to install/update msiexec if needed and then launch the MSI file.

LabView 2010 Application Builder for EXE Always Included files are not Included

In LabVIEW 2010 F2, When I am using the Application Builder to build an EXE file, I have listed 10 or so files to Be "Always Included". But when I Explore the directory where the EXE was built, those "Always Included" files are not there or in any subdirectory under the EXE file.
This frequently makes my EXE file not work properly because important files are missing. I have to spend extra debugging time to find out the the cause of my problem is missing files that the Application Builder should have transferred "Always".
Why did the Application Builder, when building an EXE target, not include the files that should be "Always Included"?
Why does the Application Builder ignore these files specifications?

Dennis Knutson wrote:
The build does include files you select. Post an example project with a small VI and some separate files where this does not happen.
No, it does not appear that all of the files that I listed in the "Always Include" list are copied during the Build process to the Build directory or any subdirectory under that.
The Build Source Files.jpg file shows most of the list of the files that should be "Always Included". Notice the .VI and .ctl files that are listed
The Build Directory.jpg file shows the file in the Build directory that were built.
The Data Directory.jpg file shows the data directory under the Build directory and may include some of the files listed in the "Always Include", but not all of them.
The other subdirectories under the Build directory were created by me and do not include any files that were copied during the Build process.
So not ALL of the files that were included in the "Always Include" list were copied into the Build directory area as expected. ALL of the files that are listed as "Always Include" should be copied, if they exist. Those files existed when then were selected for the List and they existed at the time of the Build.
I can not include an example project that demonstrates this. I am prevented from doing so by the terms of an NDA. You are going to have to take my word that this event is real and happens the same way every time. This information should be sufficient for someone to investigate why do not ALL of the files listed in the "Always Include" list are copied into the Build directory area regardless of the file type or contents.
Attachments:
Build Source Files.jpg ‏151 KB
Build Directory.jpg ‏125 KB
Data Directory.jpg ‏131 KB

Error 1305 when installing LabVIEW 7.1 app built with app builder

I have built an executable with installer from LabVIEW 7.1 app builder. The app installs/works fine, however 1 user reported 'Error 1305' when installing the app from a DOS subset on a WinXP machine. For example, a virtual drive is created using the DOS 'subst' command (see http://www.easydos.com/subst.html for more info), e.g. 'subst z: c:\temp'. Now when running z:\setup.exe, the error 1305 is encountered. If the same app is run from c:, e.g. 'c:\temp\setup.exe', it works fine. Is this a bug in the installer, or in the OS...?

Greetings,
This is an architectural issue with the Microsoft Windows Installer and Windows, and will occur with any MSI (not just those from the app builder). Under XP, a MSI cannot install from OR install to a location created by the "subst" command. My understanding of why is that installSequence runs in the context of the MSI engine, which is running as "system" user. But the subst command is a per-user setting (local to your account) so the MSI engine doesn't see it.
The only workaround is to run the MSI from a non-subst drive, or instead use network file shares (you can simulate what "subst" does by mounting an exported file share from the same machine).
Regards,
- WesW / NI

LabVIEW 2010 App Builder/Installer- Target OS Options

Similar Messages

Maybe you are looking for