Station options not copied to deployment

[jvh75021]

In my .tsd file I checked Deploy files in TS public directories as I had been told this would cause station options to be copied. However my cfg directory preference does not come across. We use a custom location instead of the default for the cfg directory so we can place it with the rest of the version controlled software. The source directories on the development machine are different then the deployment directories but I don't think this has not been a problem in the past.

Any ideas?

Thanks,

jh

[jvh75021]

Dropping this thread, will address under another title.

[Hoss183]

I'm having the same problem (background info - i'm almost a complete novice with deployments)

Whatever i do the station options are not carried accross to the deployment.

In my case its my modified sequential model thats not being used. the deploment station options always use the standard model.

i'm using a standard cfg (as far as i know) unlike the OP.

What do i need to do to the the station (and other) options to deploy?

[Hoss183]

ok, in fact i realise this is beacuse 'testexec.ini' is not being deployed from the cfg folder.

But it has created a second concern for me. There are a number of .ini files in the cfg folder that i had not previously paid attention to, but that are getting modified by my project as i can tell by the 'modified' date & time. Now since i use version control (SVN) for all source files, there are files in this c:\program filesf\NationalInstumernts/Teststand2010\Cfg folder that i am not version controlling.

How can i (and is it advisable to) move these files to my local project location, and tell TS about the new location?

[Jackie_B]

Hey Hoss,

I am not sure that I am clear about your setup, but if you are developing a sequence file through SVN, you should do the following:

Create a workspace with all dependent configuration files, sequence files and libraries (I have attached a screenshot of what this would look like). You should then upload this to SVN and allow users to make changes to files through the workspace. Once you are ready for deployment, you can download the workspace file and deploy using the workspace option. You should never replace altered configuration files with the original configuration files in your development environment, as this will affect all future development.

Having said that, if you are considering changes on a test station that has already been deployed to, you can replace configuration files once they have been altered.

Please let me know if I have thoroughly addressed your question and I hope you have a great day!

Regards,

Jackie

[Hoss183]

ok, i have selected an alternate config directory (in Config - Station options - Prefs) and TS has copied my Cfg into the same location as my project checkout.

I have selected the Cfg folder as 'from directory' source in the deloy utility, and it gets added to the distributed files.

But again the deployed (testexec) is not taking the settings - it uses the default model instead of the modified model thats specified in testexec.ini

I'm really getting frustrated with this deploy util, whenever i touch something in one place it breaks in another..

Help!

[Hoss183]

Actually in the deploy utility, is it important what i set as the destination for the Cfg folder?

At the moment i had left it at the default of 'Installation directory' but should it be somwhere else to take effect? i.e. 'TestStand directory' or other?

[Hoss183]

ok, most problems resolved now.

But one last one - How are search folders supposed to translate in deployment?

I'll explain...

I have a modified model "SequentialModel_Modified.seq' that is in my project. The location of this file (on the dev machine) is in the search folders e.g. c:\dept\group\projects\common\sequentialmodel_modified.seq

But when i make the deployement, it goes into a different location e.g. c:\test stand\common\...'

When i check the station options - model, there is the error ' file not found'

Check the search directories on the deployment shows that they are exactly as the dev machine 'c:\dept\group\...' and showing 'not found'

I would have expected the search diretories to get translated for the deployement paths. Or have i done something wrong?

[Jackie_B]

Hi Hoss,

When you add a search directory, you are adding an absolute path for which Teststand can use to access the dependent files. If the absolute path is not the same on the development and deployment machine, you should not add this path. You should keep the default of "current sequence file" and "current workspace directory" checked and this should be sufficient to find dependent files if you have included dependent files in the workspace directory, as mentioned in my previous post.

Regards,
Jackie

[Hoss183]

I have no 'current sequence file' in the search directories.

I had not realised that the .tsw file had to be at the top of a tree in the project. Due to the way i arrange my project files in SVN the work space file was down on a branch. I will try to move it up and see if that works.