Want to confirm that .NET handles the release of TestStand resources for me - unlike LabWindows\CVI

[Believer]

In my LabWindows/CVI UI I know I have to be diligent with releasing references and freeing memory when using various TestStand methods, or getting the handle from a property. Specifically using CA_DiscardObjHandle and CA_FreeMemory. If I miss something the dev. environment tells me of a memory leak at the end.

In a .NET module though, am I right in thinking that all the memory issues are taken care of and I don't have to concern myself with releasing resources?

Thanks!

Ronnie

[James_Grey · Accepted solution]

You are correct. However, in the rare instances where you have to call a TestStand method in addition to releasing a reference, you still need to call the method. In particular, I'm thinking about Engine.GetSequenceFileEx and Engine.ReleaseSequenceFileEx. I can't remember if there is another case like that one.

[Believer]

That's good news. For the rare circumstances you mention, do you know if the Visual Studio environment will inform of any memory leaks like the CVI one does?

[James_Grey]

Any leaks should be displayed on exit if Configure>>Station Options>>Preferences>>Debug Options>>Report Object Leaks is enabled.