>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

Signature
Mattias Sjögren [C# MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.
Ron M. Newman - 29 Nov 2006 21:37 GMT
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
>>1) What happens to the actual assembly.dll when the method goes out of
>>scope? will it close?
[quoted text clipped - 11 lines]
>
> Mattias
Jon Shemitz - 29 Nov 2006 21:59 GMT
> 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.

Signature
.NET 2.0 for Delphi Programmers
www.midnightbeach.com/.net
What you need to know.