<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.iis.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:cs="http://blogs.iis.net/"><channel><title>Understanding when to use a Finalizer in your .NET class</title><link>http://blogs.iis.net/tomchris/archive/2008/04/25/understanding-when-to-use-a-finalizer-in-your-net-class.aspx</link><description>A common problem we see when moving to .NET all revolves around the finalizer.&amp;#160; There are a few reasons that this happens: Developers move from C/C++ to C# and are used to created classes with a constructor and destructor. Developers don’t understand</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>Understanding when to use a Finalizer in your .NET class - Tom Christian&amp;#39;s Blog</title><link>http://blogs.iis.net/tomchris/archive/2008/04/25/understanding-when-to-use-a-finalizer-in-your-net-class.aspx#2322277</link><pubDate>Sat, 26 Apr 2008 00:42:25 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2322277</guid><dc:creator>Understanding when to use a Finalizer in your .NET class - Tom Christian's Blog</dc:creator><description>&lt;p&gt;Pingback from &amp;nbsp;Understanding when to use a Finalizer in your .NET class - Tom Christian&amp;amp;#39;s Blog&lt;/p&gt;
&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2322277" width="1" height="1"&gt;</description></item></channel></rss>