Why use LabVIEW Project with TestStand?

[DowNow_]

Hi,

Other than the LabVIEW benefits of organizing and namespacing your code modules, are there any other benefits to using LabVIEW projects and the LabVIEW Project field in the TestStand module adapter?

I've had a few bugs when using the LabVIEW project field in some steps and forgetting it in others. The LabVIEW reserved feature doesn't work the same because these steps are treated like two instances of LabVIEW. It seems like more complexity, are there good reasons for it? thanks.

cc

[snowpunter]

It provides application namespacing which allows you to call two VIs of the same name. It's also useful when using project-specific features like network variables, LV classes etc. Other than that there's not much need for it.