Consider a Form (Form1!) that resides in a Windows Application (.EXE)
and which loads a Console Library at runtime (.DLL).
The form has a few labels and a progress bar, nothing fancy. On XP when
you call
Form1.Close();
the application closes and you can delete the DLL. I have discovered a
problem on NT whereby calling Close() on the EXE does not appear to
unload the DLL, and thus I can't delete the file (this is a serious
problem in my case)
I also examined the task manager and the EXE is definitly not running
after Form1.Close() but the 'lock' on the DLL still exists!
This is a very obscure problem I know but perhaps someone can shed some
light (I'm very much in the dark)
--
Wal
http://www.vooose.com
*** Sent via Developersdex http://www.developersdex.com ***
