Thanks for the explanation. I thought I did something wrong.


>Kind of a late response, but any assembly loaded into memory by an application including an EXE will never release completely unless you shut down the AppDomain or shut down the application.
>
>This means effectively that the file stays loaded always, but related resources for objects get cleaned up by the garbage collector.
>
>As a general rule - if a class implements IDisposable() it's a good idea to call .Dispose() explicitly from VFP code to ensure that objects are properly releasing additional and non-.NET resources.
>
>Hope this helps,
>
>
>+++ Rick ---
>
>>Hello,
>>
>>I am using the NET Extender in VFP and have the following question:
>>
>>How can I clean up properly the resources when I use an assembly.
>>
>>For instance I have an assembly that has a class:
>>

>>lcAssembly = "XEngine.exe"
>>lcClass = "xEngine.Form1"
>>loNetObj = CLRNewObject(lcClass,lcAssembly)
>>loNetObj.Show()
>>

>>now to close the form I issue:
>>

>>loNetObj.Close()
>>

>>But the XEngine.exe is still loaded somehow in memory. How can I clean up the resources?