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 to dispose these, so they have to be disposable as well, etc. The only way to avoid it is to:
- avoid using IDisposable classes where possible, lock or wait for events in single places, keep expensive resources in single place, etc
- create them only when you need them and dispose them just after (the
In some cases IDisposable can be ignored because it supports an optional case. For example, WaitHandle implements IDisposable to support a named Mutex. If a name is not being used, the Dispose method does nothing. MemoryStream is another example, it uses no system resources and its Dispose implementation also does nothing. Careful thinking about whether an unmanaged resource is being used or not can be instructional. So can examining the available sources for the .net libraries or using a decompiler.