07-30-2007 10:21 AM
07-30-2007 04:07 PM - edited 07-30-2007 04:07 PM
Yes, you can call the method Engine.UnloadAllModules. One way this call could be added would be to add the postUUT callback to your sequence file and then add an ActiveX/COM action using this method to the postUUT sequence.
The TestStand API Reference Guide located in the TestStand help has information on this method and many others. Searching within the TestStand help for "unload modules" will also return more information about this method.
Feel free to ask if you need help creating a callback or doing a method call.
Message Edited by Dillon G on 07-30-2007 04:08 PM
12-12-2013 02:50 PM
So what Object Reference should be used when using this method (Engine.UnloadAllModules)?
12-12-2013 02:56 PM
You can use a Statement step in TestStand and simply use RunState.Engine.UnloadAllModules().
12-12-2013 03:13 PM
Daniel,
The problem I am having is I am getting an error when I close TestStand (see attachment), but when I use the File pull-down menu to Unload All Modules, the problem goes away???
12-13-2013 04:07 AM
This would suggest that you are not deallocating memory / closing references in one or more of your code modules (vi, dll may be?)
I would skip some sections of the code to narrow it down.
01-02-2014 11:21 AM
That can sometimes happen if you have code that is attempting to call into a dll after it has already been unloaded. That should normally not ever happen. But perhaps you have code that calls into a dll when something gets cleaned up for shutdown that doesn't own a strong reference to a dll or appdomain thus not keeping it loaded.
-Doug