Is IDisposable.Dispose() deterministic for managed resources?

[antoan]

For instance:

component.Dispose(); will this lead to resources beginning to be
released immediately after the method is called, as opposed to relying
on GC?

[Lloyd Dupont]

Roughly it will release resourece immediately.

Concretely it will only release immediately resource that can be relesed
immediately, that is native resource.
Managed memory use by the managed object will only be claimed when:
1. the object will stopped being referenced
2. and the GC kicks-in...

"antoan" <an****@antoan.plus.com> wrote in message
news:44***********************@ptn-nntp-reader01.plus.net...

For instance:

component.Dispose(); will this lead to resources beginning to be released
immediately after the method is called, as opposed to relying on GC?

[Mattias Sjögren]

>component.Dispose(); will this lead to resources beginning to be

released immediately after the method is called, as opposed to relying
on GC?

Dispose will release native resources held directly or indirectly. It
will not affect when an object is garbage collected.
Mattias

--
Mattias Sjögren [C# MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

[Mark Wilden]

"antoan" <an****@antoan.plus.com> wrote in message
news:44***********************@ptn-nntp-reader01.plus.net...

For instance:

component.Dispose(); will this lead to resources beginning to be released
immediately after the method is called, as opposed to relying on GC?

If you mean managed resources created by "component", they'll be released
(Dispose'd) in Dispose only if you make it so.

Or I misunderstood you. :)

///ark