Prev: A Review question from the Microsoft book(exam 70-536)
Next: Determine framework version used by an application or a .dll
From: Tony Johansson on 1 May 2010 17:05
Hi!

This is some text from book professional C# 2005.
"Application domain are an extremely useful construct if assemblies are
loaded
dynamically, and the requirement exists to unload assemblies after use.
Within the primary application domain it is not possible to get rid of
loaded assemblies. However, it is possible to end application domain where
all assemblies loaded just within the application domain are cleaned from
the memory."

The text say in one part "Within the primary application domain it is not
possible to get rid of loaded assemblies" but I mean if you stop a process
will the result as I believe be that it is removed from memory ?
I'm I correct

//Tony


From: Arne Vajhøj on 1 May 2010 20:54
On 01-05-2010 17:05, Tony Johansson wrote:
> This is some text from book professional C# 2005.
> "Application domain are an extremely useful construct if assemblies are
> loaded
> dynamically, and the requirement exists to unload assemblies after use.
> Within the primary application domain it is not possible to get rid of
> loaded assemblies. However, it is possible to end application domain where
> all assemblies loaded just within the application domain are cleaned from
> the memory."
>
> The text say in one part "Within the primary application domain it is not
> possible to get rid of loaded assemblies" but I mean if you stop a process
> will the result as I believe be that it is removed from memory ?
> I'm I correct

You are correct.

But they are talking about a permanently running process.

For a long running processes it can occasionally be desirable
to unload a DLL to load a new.

Arne
 | 
Pages: 1
Prev: A Review question from the Microsoft book(exam 70-536)
Next: Determine framework version used by an application or a .dll