Assemblies and acope

[Ron M. Newman]

Hi,

If I declare an assembly within a method and call ".Load" on it...

public void foo()
{
Assembly asm = Assembly.Load("myassembly.dll");
}

1) What happens to the actual assembly.dll when the method goes out of
scope? will it close?
2) what would happen to types I instantiate that are in that assembly? will
they "survive" and be healthy? (providing of course they're still in scope)

thanks,
Ron

 

[Mattias Sjögren]

1) What happens to the actual assembly.dll when the method goes out of
scope? will it close?

No. The only time an assembly is "closed" or unloaded is when the
appdomain is unloaded.

2) what would happen to types I instantiate that are in that assembly? will
they "survive" and be healthy? (providing of course they're still in scope)

The objects you create will stay in memory as long as they are
referenced.


Mattias

 

[Ron M. Newman]

So: just to see if I got it right... the assembly is loaded in the method,
referenced there by a temporary reference, and when that reference goes out
of scope nothing really happens as it's also referenced by the main app
domain which holds it. It can be easily referenced back using the app domain
API's

Ron

 

[Jon Shemitz]

So: just to see if I got it right... the assembly is loaded in the method,
referenced there by a temporary reference, and when that reference goes out
of scope nothing really happens as it's also referenced by the main app
domain which holds it. It can be easily referenced back using the app domain
API's

Yes.