07-13-2006 10:44 PM
07-13-2006 11:08 PM
07-13-2006 11:31 PM
07-14-2006 07:44 AM
07-14-2006 09:20 AM
07-14-2006 09:36 AM
I want to comment that Dennis is exactly right about the intent of TestStand.
TestStand is meant to connect and augment code you write in LabVIEW, CVI, and/or Visual Studio, not to replace it. Also, what he refers to as putting functionality in a "custom step" can mean just calling a VI, DLL, server, or assembly from a TestStand step, not necessarily the similarly named but more involved process of creating a custom step type.
Custom step types are good for wrapping a function or VI with a user friendly configuration dialog to facilitate re-use. However, in many cases it is more than adequate to simply passing arguments to a code module you call directly.
It is certainly true that having a large number of code module files can make it more difficult to move a sequence without forgetting to include one of its dependencies. The TestStand deployment tool is designed to help mitigate this problem by identifying dependencies and packaging them all into one directory or installer.