idisposable

I have a class which starts a Task and want to ensure that the Task stops when the object is garbage collected. I have implemented the IDisposable pattern to ensure that if the object is disposed manually or used within a using block, then the Task stops correctly. However , I cant guarantee that the end user will call Dispose() or use the object within a using block. I know that the Garbage Collector will eventually call the Finalizer - does this mean that the task is left running? public class MyClass : IDisposable { private readonly CancellationTokenSource feedCancellationTokenSource = new

I'm trying to make sure that my understanding of IDisposable is correct and there's something I'm still not quite sure on. IDisposable seems to serve two purpose. To provide a convention to "shut down" a managed object on demand. To provide a convention to free "unmanaged resources" held by a managed object. My confusion comes from identifying which scenarios have "unmanaged resources" in play. Say you are using a Microsoft-supplied IDisposable -implementing (managed) class (say, database or socket-related). How do you know whether it is implementing IDisposable for just 1 or 1&2 above? Are

I am aware that all objects which implement IDisposable should be disposed of as soon as they are no longer needed in order to free the memory used by their unmanaged resources. My question relates to objects which I know for a fact will live until the host process itself is terminated. Would it make any difference if I dispose of them or not? Is there any chance of memory not being freed when the process dies? What about GDI objects? Would the GDI handles be freed when the process dies even if they were not disposed? I fully understand that it is good practice to dispose of all objects

How is it possible for the System.ServiceModel.ClientBase abstract class to implement IDisposable Interface if the Dispose() Method declaration is not visible/declared? If I try to do the same I get an error and can't compile abstract class ATeste : IDisposable { } 'ATeste' does not implement interface member 'System.IDisposable.Dispose()' I'm using VS 2010 and Framework 4.0. Check the ClientBase declaration: // Summary: // Provides the base implementation used to create Windows Communication Foundation // (WCF) client objects that can call services. // // Type parameters: // TChannel: // The

Coming from C/C++ a long time ago I still have a habit of ensuring that all resources are cleaned up correctly. I always ensure Dispose is called on IDisposable classes and implement Dispose patterns in my classes containing disposable objects. However, in my environment I'm more or less the only one doing this. Others just don't understand what I'm doing and think my code is more difficult to understand. They just create database connections, open streams etc without calling Close or Dispose. Sometimes they set a local or member variable to "Nothing" at the end of a method (guess their

I have been fixing some memory leak issues in a winforms application and noticed some disposable objects that are not Disposed explicitly (developer hasn't called Dispose method). Implementation of Finalize method also doesn't help because it doesn't go in if (disposing) clause. All the static event unregistering and collection clearing have been put in if (disposing) clause. The best practice is calling the Dispose if the object is disposable, but unfortunately this happens sometimes If there are unmanaged objects, static event handlers and some managed collections that needs to clear when