Include plug-in child classes to a deployment package

[Pulp]

When deploying from a workspace file, TestStand analyses the VIs it has to include in the deployment package. However, when working with plug-in classes, TestStand will add the parent of a plug-in class, but not its children. Possibly because these are not directly used (they are included at runtime), and thus not recognised during analysis.

I would like to see that TestStand recognises a parent class it includes in the deployment, and then:

• includes all its child classes that are in the same project file;
• asks to include possible child classes that are not in the project file.

[WireWeaver]

I'm declining this idea due to lack of community support