deployment of LabVIEW User Interface

[mrbean]

I'm creating a deployment in TestStand.  I want to distribute to the target those files that are customized (found in \User\... folders) and the customized (LabVIEW-based) TestStand Operator Interface.  I noticed on page 14-12 of the TestStand Reference Manual (step 5) that it says to "Select both TestExec.exe and TestExec.uir and click Add".  Obviously this is for the CVI-based OI.  For the LabView version, do I only need to distribute the TestExec.exe, or do I also need the TestExec.aliases and TestExec.ini files.  Anything else I need for this portion of the deployment?

[KristenC]

Hello Mr Bean,

To deploy the files in your User directory you just need to make sure Deploy Files in TestStand User Directory is checked on the System Source tab of the TestStand Deployment Utility. 

When adding the files to your project for your custom OI you will of course need the .exe.  The .aliases file, according to the LabVIEW help, is a "File that maps targets to URLs. The URL varies by target. Usually, the URL for a target on a network is an IP address. Targets on serial ports display the URL as the serial port."  I believe it is mostly used for Shared Variables.  The .ini file has all the configurations for the LabVIEW runtime.  There is no harm in including them all, but the .aliases and .ini files may not be necessary depending on what you are doing in your OI. 

[mrbean]

I saw the Deploy Files in TestStand User Directory checkbox, but I'm getting my files (that will go in the \user folders) from configuration management.  I don't want the tool to get them from my PC.  Hopefully this is not a problem

[Teds]

Bean

I ran into the same issue with custom User files for TestStand.   You do NOT need to select the checkbox, if you are already deploying your User files (from a CM tool) you can simply have the TestStand deployment utility deploy them to the <TestStand>\Components\User directory.    You must remember to have all your custom user files in your TestStand workspace file (*.tsw).

or Option 2

Otherwise you can obtain your files from CM and manually move them to the TestStand user directories on your PC and then check the box to have TestStand deploy them.  In this example, you do NOT need these files in your TestStand workspace (*.tsw) file.

Because I kept forgetting to copy over the files as in Option 2, I went with the first suggestion and did not check the box.

Paul Holzrichter

Message Edited by Teds on 06-02-2008 01:02 PM