Thanks Viv, I'll test it...

>Hi,
>
>Will this help: http://www.guidanceshare.com/wiki/Interop_(.NET_1.1)_Performance_Guidelines_-_Marshal.ReleaseComObject
>
>Regards,
>Viv
>
>>I am accessing net (c#) classes via VFP9 successfully. However, garbage cleanup is a mess. I've noticed that setting the object in VFP to null and releasing it does not really release them. If I null and release my objects, I cannot rebuild the dotnet dll until I shut down VFP completely and even then, my machine will be sluggish after instantiating a lot of .net objects via com interop. I know that .net uses the .net garbage collector to release an object so how do I cleanup from VFP? What has to be visible via com interop to VFP in order for me to destroy the .net objects I create in VFP that are accessible to me via com interop? Something has to release the objects and even shutdown the .net runtime from VFP...