"Mohamoss" <mohamed.mossad@egdsc.microsoft.com> wrote in message
news:rWVdWO89DHA.2100@cpmsftngxa07.phx.gbl...
> Hello Sheila
> yes what you stated in your post is correct so for eample you should
> dispose unmanged resourses before termination of your program
>

"Sheila Jones" <sheilavjones@btopenworld.com> wrote in message
news:%23IkU3O69DHA.2532@TK2MSFTNGP09.phx.gbl...
> Hello,
>
> I'm trying to get my brain around the CLR! Can somebody tell me if the
> following are correct? Thanks.
>
> 1. The CLR runs each managed application in its own application domain,
but
> there can be several application domains within the same process.
>
> 2. The managed heap is shared by all application domains within the
process.
>
> 3. When an application domain terminates, any objects it created will
> continue to exist. The garbage collector is not automatically triggered.

>
> 4. Consequently, an application with objects that wrap unmanaged resources
> should dispose of them before terminating, because termination won't
> immediately release the resources (unlike with unmanaged applications).
>
>

"Sheila Jones" <sheilavjones@btopenworld.com> wrote in message
news:OV2EEbF#DHA.3848@TK2MSFTNGP10.phx.gbl...
> Hello, thank you so much for your helpful reply. I have a couple of
> follow-on questions.
>
> 1. Does each application domain have its own garbage collector, or is
there
> just one for all app domains in the process (since there is just one
heap)?
>
> 2. When the garbage collector is triggered by an app. domain terminating,
> does it garbage collect the whole heap (including objects from any other
app
> domains), or just the objects from the terminating app domain?
>
> 3. Is the CLR absolutely guaranteed to run any pending finalizers when an
> app domain terminates?
>
>

"Sheila Jones" <sheilavjones@btopenworld.com> wrote in message
news:OV2EEbF%23DHA.3848@TK2MSFTNGP10.phx.gbl...
> Hello, thank you so much for your helpful reply. I have a couple of
> follow-on questions.
>
> 1. Does each application domain have its own garbage collector, or is
there
> just one for all app domains in the process (since there is just one

>
> 2. When the garbage collector is triggered by an app. domain terminating,
> does it garbage collect the whole heap (including objects from any other
app
> domains), or just the objects from the terminating app domain?
>

> 3. Is the CLR absolutely guaranteed to run any pending finalizers when an
> app domain terminates?
>

"Dave" <noSpamdlevineNNTP2@wi.rr.com> wrote in message
news:%23PWgskA%23DHA.1392@tk2msftngp13.phx.gbl...
>
> "Sheila Jones" <sheilavjones@btopenworld.com> wrote in message
> news:%23IkU3O69DHA.2532@TK2MSFTNGP09.phx.gbl...
> > Hello,
> >
> > I'm trying to get my brain around the CLR! Can somebody tell me if the
> > following are correct? Thanks.
> >
> > 1. The CLR runs each managed application in its own application domain,
> but
> > there can be several application domains within the same process.
> >
> > 2. The managed heap is shared by all application domains within the
> process.
> >
> > 3. When an application domain terminates, any objects it created will
> > continue to exist. The garbage collector is not automatically triggered.
>
> Not true. Objects that are created in that appdomain are destroyed along
> with that appdomain. First all unreachable objects are reclaimed, then
> objects that are still rooted but belong to that appdomain are finalized.
> The GC runs through several cycles when an appdomain is destroyed.
>
> >
> > 4. Consequently, an application with objects that wrap unmanaged
resources
> > should dispose of them before terminating, because termination won't
> > immediately release the resources (unlike with unmanaged applications).
> >
> >
> This is complicated. Generally speaking you want managed objects that wrap
> unmanaged to implement both a finalizer and a Dispose pattern. Normally
you
> should use the Dispose method and use the finalizer as a backstop. If you
> create an object in the context of an appdomain then when the appdomain is
> destroyed all those objects are destroyed along with it; this implies that
> their finalizers will run and release the unmanaged resources.
>
>