Best practice for workspaces and projects

[Ryan_G_EE]

It seems from the NI documentation that I've read, we should be organizing multiple projects within a single workspace. However, as we are getting ready to deploy one project and start another, we can't figure out how to deploy a single project from a workspace containing multiple projects...What is the best practice?

[2Shanez]

Hi R. Gibson,

From what I have found online and by trying it out, I haven’t found a way to deploy a single Project from within a Workspace. It seems like the Workspace file is meant to serve as an easy way to bundle and organize projects that would be deployed together. A good practice would be to keep the scope of each Workspace narrowed down to one deployment when designing to best take advantage of the Workspace File.

Thanks,

ShaneK 

Applications Engineering

[kosist90]

I would suggest to use for each project its own workspace. It does not make sense to mix different project within one TS workspace - b/c they are different, and will not be deployed together (although you can use shared code modules/subsequence between them, but this is a bit another topic). And I agree with 2Shanez, that workspace - is quite nice for deployment preparation, b/c it links all the needed are required files together.

But once you've created deployed image once, you can reuse TestStand Deployment configuration file (*tsd), which will contain all the needed settings for deployment.

Thus, you can use one workspace with multiple projects, and prepare deployment for each of them (b/c at the end you just need to be carefull with selecting of what VIs/sequences will be deployed, and their folder structure, etc.), and for each of them save tsd file. And, afterwards, do updates of deployment already not based on workspace file, but based on tsd-file.