The reliable solution is catching the ObjectDisposedException. The solution to write your overridden implementation of the Dispose method doesn’t work, since there is a race condition between the thread calling Dispose method and the one accessing to the object: after having checked the hypothetic IsDisposed property , the object could be really disposed, throwing the … Read more
No – default implementation of IDisposable pattern does not support it
A finalizer (aka destructor) is part of garbage collection (GC) – it is indeterminate when (or even if) this happens, as GC mainly happens as a result of memory pressure (i.e. need more space). Finalizers are usually only used for cleaning up unmanaged resources, since managed resources will have their own collection/disposal. Hence IDisposable is … Read more
Yes, Dispose will be called. It’s called as soon as the execution leaves the scope of the using block, regardless of what means it took to leave the block, be it the end of execution of the block, a return statement, or an exception. As @Noldorin correctly points out, using a using block in code … Read more
Interesting blog post here: Dispose of a WPF UserControl (ish) It mentions subscribing to Dispatcher.ShutdownStarted to dispose of your resources.
There is a discussion about this in the MSDN forums. Stephen Toub, a member of the Microsoft pfx team has this to say: Task.Dispose exists due to Task potentially wrapping an event handle used when waiting on the task to complete, in the event the waiting thread actually has to block (as opposed to spinning … Read more
If you are using .NET Framework 4.5 or later, there is a StreamWriter overload using which you can ask the base stream to be left open when the writer is closed. In earlier versions of .NET Framework prior to 4.5, StreamWriter assumes it owns the stream. Options: Don’t dispose the StreamWriter; just flush it. Create … Read more
You can’t really “prevent” IDisposable from spreading. Some classes need to be disposed, like AutoResetEvent, and the most efficient way is to do it in the Dispose() method to avoid the overhead of finalizers. But this method must be called somehow, so exactly as in your example the classes that encapsulate or contain IDisposable have … Read more
The .Net Garbage Collector calls the Object.Finalize method of an object on garbage collection. By default this does nothing and must be overidden if you want to free additional resources. Dispose is NOT automatically called and must be explicity called if resources are to be released, such as within a ‘using’ or ‘try finally’ block … Read more
Here are a couple of discussions explaining why Dispose is not necessary for a DataSet. To Dispose or Not to Dispose ?: The Dispose method in DataSet exists ONLY because of side effect of inheritance– in other words, it doesn’t actually do anything useful in the finalization. Should Dispose be called on DataTable and DataSet … Read more