TestStand 3.5 Deployment Problem

[WrightSwri]

Problem Description :

I have a TestStand deployment file that I am trying to run.  It installs everything ok except for the Callbacks folders.  I have custom

StationCallbacks and FrontEnd callback sequences in the User folder.

When I run my installer on a target computer, I watch the subdirectories to see if my custom callbacks get installed in the Users folder.  When the installer says “Installing item 1 of 4…” I see my custom callbacks go in the User folders.  When the installer says “Installing item 3 of 4…”, I see my StationCallbacks.seq file get replaced by the default StationCallbacks.seq file.  I know it changes because the file size goes from 93kb (mine) to 2kb (default).  How can I prevent this from happening?  

Here’s some other info:

1. I use a single deployment file to install both my application and the Teststand Engine.  My application consists of a custom LabVIEW GUI and some other VIs.

2. I am using the Deployment Tool for TestStand and I have the box for Deploy Files in TestStand User Directories checked.

Thanks 

Matt

[Lars_L]

Hey Matt,

I know we worked on this issue over email and phone but I wanted to pass the information along to the web for future customers. After troubleshooting this issue, it was discovered that this is, in fact, a bug, and it was reported to R&D (#51705) for further investigation. The reason why it overwrites the FrontEnd and Station Callbacks is because the deployment includes both the custom files and the TestStand Engine (this is an installation option). What it ends up doing is it incorrectly installs the custom callbacks first and then installs the TestStand Engine. One way to get around this would be to build two installers (one that installs just the Engine and one that does your normal install). To make it even simpler, you could also use a batch file to execute these two installers sequentially.

Regards