Dynamic creation of object problem

[Harry F. Harrison]

Hi all...

During startup of an ASP.NET app, I have code that dynamically goes out and
loads assemblies, looking for objects that implement a particular interface.
This code works fine, EXCEPT, the objects do not get unloaded out of the
ASPNET_WP process when I end the application during debugging, and come back
to Visual Studio. I have to manually kill the ASPNET_WP process in order to
re-build the dlls, as they are locked - something that normally shouldn't
happen, but is.

Any ideas? I've thought about loading the objects into another AppDomain,
but it seems like a lot of extra work everytime I want to load objects
dynamically under ASPNET.

[Scott Allen]

Hi Harry:

ASP.NET makes a shadow copy of the assemblies it loads, that way
assemblies in the bin directory are never locked by the worker
process.

Using Assembly.Load to dynamically load an assembly does lock the
assembly. There is no way to unload an assembly from an app domain.
Unfortunately, using another application domain might be your only
option if you want to avoid cycling the worker process

--
Scott
http://www.OdeToCode.com

On Tue, 10 Aug 2004 10:47:36 -0700, "Harry F. Harrison"
<Ha************@sbcss.k12.ca.us> wrote:

Hi all...

During startup of an ASP.NET app, I have code that dynamically goes out and
loads assemblies, looking for objects that implement a particular interface.
This code works fine, EXCEPT, the objects do not get unloaded out of the
ASPNET_WP process when I end the application during debugging, and come back
to Visual Studio. I have to manually kill the ASPNET_WP process in order to
re-build the dlls, as they are locked - something that normally shouldn't
happen, but is.

Any ideas? I've thought about loading the objects into another AppDomain,
but it seems like a lot of extra work everytime I want to load objects
dynamically under ASPNET.