Suggested Location for Shared Resources?

[LVB]

Where should I place these shared resources that can be called by the following?

• Custom Steps
• TestCode
• Process Model

Another constraint: I am attempting to use LabVIEW packed project libraries which call each other, and they need to be in the same directory for deployment.

I would like to place these files in a common directory that does not require a workspace, project, or modification of the TestStand search directories.

[jallen88]

LVB,
As you are probably aware, you can add these components to your own custom folder hierarchy, so long as they are included as a Search Directory in TestStand.

Keep in mind that the order of these folders is important. Items are searched first in the folders nearest the top of the list. For more information on configuring Search Directories, please see the following Best Practices for Improving NI TestStand System Performance.

Additionally, I highly recommend reading NI TestStand Advanced Architecture Series, specifically the section on Shared Drive Deployment Reference Architecture

[LVB]

---

@jallen88 wrote:

LVB,
As you are probably aware, you can add these components to your own custom folder hierarchy, so long as they are included as a Search Directory in TestStand.

Additionally, I highly recommend reading Developer Zone Tutorial: NI TestStand Advanced Architecture Series, specifically the section on Shared Drive Deployment Reference Architecture

---

Jared,

Thanks for the response.  I am aware of search directories.  I currently have these shared resources in the root of my workspace (the first default search directory).  This allows me to use different versions of the shared resources based upon my projects.  However, it seems to be causing issues during deployment.

My deployment systems are running a custom sequence editor.  This custom sequence editors (Full-Featured) do not seem to have the concept of a workspace or project.  Can you provide some information on how a custom sequence editor's search algorithm works differently than a development system with the concept of workspaces and projects?  I think TestStand is trying to duplicate my shared resouce files due to the lack of support for workspaces in deployment.  I do not want my shared resources files to be duplicated.

---

@jallen88 wrote:

Additionally, I highly recommend reading Developer Zone Tutorial: NI TestStand Advanced Architecture Series, specifically the section on Shared Drive Deployment Reference Architecture

---

This article seems like a good start, however it lacks in detail:

• What files should I place under the "Resources" folder?  
• Where are projects and workspaces mentioned?

It would be great if there could be an "example project" that demonstrates the suggestions from this article.

Regards,

Brian

[jallen88]

Brian,
In TestStand, Workspaces are used to organize all the files in a TestStand system. A workspace consists of one or more projects, each of which should have a specific functionality.

You are correct in that the User Interfaces do not understand the idea of a workspace. Workspaces are intended to be used during development. The proper way to then move this workspace to a test machine is to create a deployment for a particular workspace. This is done by enabling the From TestStand Workspace File option in the Deploy Files section on the System Source tab of the TestStand Deployment Utility.

Please read the following article for more information: NI TestStand Help: Using a TestStand Workspace File to Create a Deployment.

[James_Grey]

"the User Interfaces do not understand the idea of a workspace"

... that might be a little strong. You can access the workspace from a UI with File>>Browse Workspace...