TestStand Deployment Fails when Deploying Dynamic Dispatch VI

This Document is not yet Rated

Primary Software: TestStand
Primary Software Version: 3.1
Primary Software Fixed Version: N/A
Secondary Software: LabVIEW Development Systems>>Base Package

Problem:

I have created a LabVIEW Object-Oriented Project that contains a dynamically dispatched VI. When I try to deploy my TestStand workspace that includes these VIs, I get a warning of the following form:

Warning: The following warnings occurred while processing VIs: A name collision occurred during the build. VIs were renamed to protect the build. If any dynamic calls were made to the following VI(s), unexpected behavior may occur:

How can I properly deploy my TestStand workspace?

Solution:

To deploy your TestStand workspace, you will need to add all of the dynamic dispatch VIs to the workspace you are deploying.

When the TestStand deployment utility packages VIs, it puts all necessary subVIs into a Supporting VIs directory. However, because overriding dynamic dispatch VIs must have the same name, when copying into this flattened directory the file already exists so the deployment utility gives a warning.

To properly deploy your dynamic dispatch VIs, simply add them to your TestStand workspace. Then when you deploy the workspace, you may define where on the target machine the files should reside. Be sure to put dynamic dispatc VIs of the same name into separate folders to avoid the warning message above.

To avoid errors, all VIs should be in the same root installation directory, i.e. <TestStand>, <Program Files>, etc.

Attachments:

Report Date: 12/26/2007
Last Updated: 12/26/2007
Document ID: 4GPCI4T3

Your Feedback!

Poor | Excellent

Yes

Document Quality?

Answered Your Question?

Please Contact NI for all product and support inquiries.