TestStand won't save .tsw

[jvh75021]

Modified my .tsw and selected save. Viewed directory and it still had old date. Same using "save as". Saved it under a different name and then used Explore to rename it. This worked. Closed and re-opened TS and the new .tsw which showed the changes.

Checked file into clearCase. A co-worker tried to use it but kept seeing the old version. After he got my latest .tpj he could see the updated .tsw.

The first problem seems like a file handle problem. The 2nd baffles me.

thanks,

jvh 

[dug9000]

I think you might be misunderstanding what a tsw file stores. A tsw file stores which projects you have specified. It is the tpj files which store the files you put into the projects. So if you didn't add any projects to the workspace then the tsw file hasn't changed and doesn't need to be saved. If you added files to a project. that project then is modified and needs to be saved, but the workspace file itself does not.

Hope this helps clarify things,

-Doug

Message Edited by dug9000 on 04-06-2010 10:00 AM

[jvh75021]

Thanks for the reply but everything is now as clear a thick, homogeneous solution of soil in water.

This TS software was developed by a "Certified" NI partner. He placed binary files in the tsw that TS via LV needed to download to the UUTs. Since I was adding some binaries I assumed it had to be that way.

I will think about your reply and study up on these file types. Hopefully the solution will settle and stratify with time.

Thanks again,

jvh 

[dug9000 · Accepted solution]

Maybe my explanation was unclear. When you add a file to the workspace, unless it is a project, you are really adding it to the project file under which it exists. The workspace refers to project files and the project files are what you generally insert other files into. Thus when you save the workspace what it really does is save any modified project files and the workspace itself if you added/removed/edit what projects it contains. What you see in the workspace view is really the combination of what exists both in the tsw file and in the project files.

There is nothing wrong with putting binary files in the project files. You can put whatever files you like in the project files and this is useful both for source control and deployment. The point I was making is that the tsw file itself only stores the locations of the project files it's showing. It is the project files that store the locations of the files that are listed underneath them.

-Doug

Message Edited by dug9000 on 04-07-2010 09:30 AM