How to load modified versions of the stock Plugins

[Jed_Davidow]

I want to modify NI_ReportGeneration.seq.  I know I could probably spin off a whole new plugin, but baby steps here.

I have set up a new environment, and teststand loads almost everything from there.  ModelSupport.SEQ is loading from the new environment.  And TS copied over the NI_ReportGeneration plugin when those were created (To "env\CommonAppData\Cfg\ModelPlugins\Cfg\ModelPlugins").  However the cache plugins step of the Initialize Model Plugins sequence loads the one in the TS program directory, not the one in my environment.

It appears that this is the default location, and it's not scanning through the open file in the workspace or the search paths to find it.  It looks like I could specify the relative path from modelsupport via a CFG file, but I am not sure where to do this.

Anyone know?

[Oli_Wachno]

TestStand uses the SearchPath settings to find stuff.

By default, it is configured to first search the files from %TestStandPublic% directory. If your .tsenv file is configured correctly, it will point to the environment directory.

If TestStand doesn't find the stuff it needs there, it will go through the rest of the search directories, e.g. %TestStand%

My guess is that the seqeunce you are referring to is not cached, but rather not in (in the right location within) your environment directory structure

Can you double check?

[Jed_Davidow]

Yeah, I thought of that, but I am not sure...

1) I copied all the model files to my workspace, and I have the workspace path in the search paths above all the TS paths.

2) However, if the TX components folder is in the search paths, it will supersede my paths, even if they are higher in the order.

3) OK, fine.  I duplicated the components folder to my project, so I can just exclude the TS components path, right?  Well this partially works.  When I uncheck the TX components folder, it loads my copy of the plugin from my workspace.  but...

4) It then chokes and can't find some of the core TS components in the BIN folder.  "Well, why would you exclude the bin folder from the search paths?!" you might ask.  And you're right... because I didn't.  But when I exclude the components folder it appears that the BIN folder is also excluded, even though it's actually checked!

Maybe I need to play with the order again?