Hello Mr. Bean,
By default, NI's process models store code module path as a relative path. So, the path to the ModelSupport2.dll is stored as
ModelSupport2.dll instead of
C:\Program Files\National Instruments\TestStand 4.0\Components\NI\Models\TestStandModels\ModelSupport2.dll. TestStand finds this file by appending the relative path name to all of the search directories until it finds a file. If your target computer has the default search directory of
C:\Program Files\National Instruments\TestStand 4.0\Components\NI\ enabled to search through all sub-directories (which it should), then your custom process model should not have a problem locating ModelSupport2.dll and all of the other model support components.
You can also deploy your search directories by including
<TestStand>\cfg\TestExec.ini in your workspace (and then in your deployment), as your search directories are stored in TestExec.ini.
Also, "TestStand 4.0" can be replaced with "TestStand <version>" for the above paths. I hope this helps!
Best Regards,
Software Engineer
Jett R