DotNetKicks.com - Stories tagged with dispose

What If I Don't Call Dispose() on my LINQ to SQL DataContext Object?

Wed, 20 Aug 2008 22:05:41 GMT

Steven Walther recently posted on the subject of disposing of DataContext objects and provided some interesting insight into what actually happens. From what he says it sounds like the DataContext object acts much like the SqlDataAdapter class. It opens the connection right before a query is executed and closes it immediately after. I don't want to steal Steven's thunder so check out his post on the subject (the last part of the article talks about the consequences.or lack of consequences.of not calling Dispose()).

CA1816 - Dispose Pattern

Tue, 06 May 2008 04:15:27 GMT

Warning CA1816 : Microsoft.Usage : Change 'xxx.Dispose()' to call 'GC.SuppressFinalize(object)'. This will prevent unnecessary finalization of the object once it has been disposed and it has fallen out of scope.

Things you MUST dispose

Wed, 02 Apr 2008 08:46:02 GMT

When the .NET Framework instantiates an object, it allocates memory for that object on the managed heap. The object remains on the heap until it's no longer referenced by any active code, at which point the memory it's using is reclamed by the Garbage Collector (GC). Before the GC deallocates the memory, the framework calls the object's Finalize() method, but developers are responsible for calling the Dispose() method.