Unmanaged DLL staying loaded in NUnit GUI

I'm having some trouble with a Visual Studio 2005 project consisting
solely of unit tests. The code under test requires an unmanaged DLL (via
P/Invoke declarations), which is copied to the output directory.
Obviously, it's then copied to the test project's output directory, but
if NUnit is open, and has just run those tests, then somehow the
unmanaged DLL is still loaded, and I can't build the test project again
w/o killing NUnit entirely (loading a different, unrelated test project
into it doesn't solve the problem). Perhaps someone has seen this
before? I could investigate in more detail, but perhaps someone knows
what's going on here? I'm not suggesting that this is NUnit's problem;
it may be that unmanaged DLLs are loaded into a process, not an
AppDomain, and then not unloaded (I'm guessing). 
 
The usual error message: "Unable to copy file
"D:\trunk\CommonFunctionality\Third-Party\Bin\lpsolve55.dll" to
"bin\Debug\lpsolve55.dll". The process cannot access the file
'bin\Debug\lpsolve55.dll' because it is being used by another process."
 
________________________________


Tony Nassar

Cell: (703) 994-0954

Blog: http://slideguitarist.blogspot.com/
<blocked::http://slideguitarist.blogspot.com/> 
Music: http://www.soundclick.com/thecompletists
<http://www.soundclick.com/thecompletists> 



"God love me, and I'm a hell of a fighter.." - Floyd Mayweather

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

_______________________________________________
Nunit-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nunit-users