How can I create a complete dependency list from a TestStand 4.2.1 workspace?

[GeoffA]

This would be used for software configuration management functions and Perforce labeling to ensure an accurate snapshot of a build coming from the TestStand Deployment Utility.

[~jiggawax~ · Accepted solution]

I think your best bet is to just build a deployment and then create a tool to go through the Image hierarchy to get a list of all the files.  When you create a deployment you get the Image folder and the Installer.  The Image folder should contain all of the dependencies throught its hierarchy.

The problem with just straight up analyzing your workspace is that it doesn't take into account the sub modules of directly called code modules.  Depending on if you were using LabVIEW, .NET or CVI then you have to call into their APIs to continue searching for sub modules.  That is if you wanted to automate it.  Not to mention it wouldn't know any of the dynamically called dependencies.

Hopefully this helps,

[GeoffA]

Good idea, jigg. Come over for a BBQ.