Academic Company Events Community Support Solutions Products & Services Contact NI MyNI
12 ratings:
 3.41 out of 5   

Copying a Release Executable in LabWindows™/CVI to a Different Computer



Primary Software: LabWindows/CVI Development Systems>>Full Development System
Primary Software Version: 2009 SP1
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem:
I created a fully functional program using the LabWindows/CVI development environment and then created a release executable by selecting Build » Create Release Executable. I then copied the executable over to another computer and tried to run it. The program did not run, but returned an error saying it could not find the user interface (*.uir) file. When I create a release executable in LabWindows/CVI, are all the necessary components included in the executable (*.exe) file? Why can't I just copy the executable to another computer and run it?

Solution:
There are several reasons why an executable copied from one machine to another machine might not work.

First, the LabWindows/CVI Run-time Engine is required on all machines that will run a LabWindows/CVI built executable. If the target machine already has the LabWindows/CVI Run-time Engine, be certain that the version of the Run-time Engine matches or exceeds the version of the LabWindows/CVI development environment in which the executable was created. For example, an executable created in LabWindows/CVI 8.0 will not run on a machine with a LabWindows/CVI 7.0 Run-time Engine. The latest LabWindows/CVI Run-time Engine can be found on the LabWindows/CVI Drivers and Updates page.

Second, all files that the executable utilizes must be included on the target machine. For example, if the LabWindows/CVI project has a user interface, then this file must be available to the executable. If you do not wish to distribute your user interface file with your application, the option to embed your user interface into your executable is available. To set this option, select Build » Target Settings and then place a checkmark next to the Embed Project .UIRs option.

(Note: Make sure to include all .uir files loaded through LoadPanel or LoadPanelEx in your project if you want to ship only the executable file. You must pass a simple filename to the functions LoadPanel or LoadPanelEx if you are using the embed user interface option. If you are using absolute paths, these functions will always look on disk for the .uir file.)

The safest approach to making sure that all necessary files are included on the remote machine is to create a distribution kit for your project. Select Build » Distributions to create a distribution kit.

For further information on what files need to be included on the target computer, refer to the LabWindows/CVI Help (Help » Contents) and browse to
  • Contents » Programmer Reference » Creating and Distributing Release Executables and DLLs
  • Contents » Using LabWindows/CVI » Managing Projects » Building a Project » Distributing Applications


Related Links:
Drivers and Updates: LabWindows/CVI
Developer Zone Tutorial: Customizing Create Distribution Kit Installers in LabWindows/CVI
KnowledgeBase 1AL89INU: How Do I Debug a CVI Distribution Kit Installation?
KnowledgeBase 2CRG1S5T: How Do I Determine the Version of My CVI Run-Time Engine?

 



Attachments:





Report Date: 11/19/2001
Last Updated: 05/30/2012
Document ID: 2FI9N1M9

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
  1 2 3 4 5
Please Contact NI for all product and support inquiries.submit