When a managed DLL makes a call to an unmanaged DLL what controls the
lifetime of the unmanaged DLL? I am assuming when I make the first call to
an unmanaged DLL, the unmanaged DLL is loaded into memory and stays in memory
(meaning global variables are maintained). How does to unmanaged DLL know
when to unload? Are there any technical articles that discuss this?
"Peter Huang" [MSFT] - 30 Jun 2005 02:37 GMT
Hi
Here is a link for your reference.
PInvoke Library Load/Unload Behavior ¡§C Freeing Unmanaged Libraries
http://blogs.msdn.com/robgruen/archive/2004/11/12/256199.aspx
Best regards,
Peter Huang
Microsoft Online Partner Support

Signature
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.