Ok from what I am reading, the Finalizers are not automatically created. However, if a Finalizer is used, the GC.SupressFinalize() method will speed up the process of cleaning up resources by not calling the finalizer. Better yet, implement the IDisposable interface and do your clean up there.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Russell Collins Sent: Thursday, September 06, 2007 2:26 PM To: Discussion of advanced .NET topics. Subject: RE: [ADVANCED-DOTNET] l immediately release any unneeded memory I have read it in a C# cookbook. Do you have any documentation proving otherwise?? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Johnson Sent: Thursday, September 06, 2007 1:19 PM To: Discussion of advanced .NET topics. Subject: Re: [ADVANCED-DOTNET] l immediately release any unneeded memory On 9/6/07, Russell Collins <[EMAIL PROTECTED]> wrote: > > 1. Every object has a finalizer as well as a constructor in .NET > whether you declare it or not. I believe you're mistaken. Do you have a link to some documentation of this? -- Steve Johnson =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
