DLL unload problem

[yev]

Hello,

Although I set the "unload after sequence executed" option in the step properties, the DLL that used by this step is not detached after the execution finished. TestStand detaches all DLL's only then the application closed. The same problem occurs if I am using the Active_X object with "attach to active" option.

Is it bug? How can I force TestStand to unload step modules after the sequence executed?

Thanks,

Yevgeny

[silvius]

Hello Yevgeny,

There are many reasons a DLL (or a code module) is not unloaded after sequence executes. For example:
1. The same code module is used by multiple steps, and not all the steps are having the "unload after sequence executed" option
2. The same code module is present in the next sequence to be called, and the "preload when execution begins" is set. This way the dll is not unloaded because it has to be loaded for the next sequence to execute
3. Inside the dll, some references to TS objects might not have been released

To force unloading, you can use an ActiveX step for Engine.UnloadAllModules but this will force unloading of all modules, not only on a specific dll.

Hope this helps,
Silvius