<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/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/"><channel><title>If I'm living in a managed world, why do I need Dispose()?</title><link>http://blogs.msdn.com/smaillet/pages/if-i-m-living-in-a-managed-world-why-do-i-need-dispose.aspx</link><description>It's inevitable that at some point a C/C++ programmer migrating to .NET and C# will run into the need to use Dispose() or IDisposable and ponder the reason for their existence. After all - the idea of a managed environment like .NET and a language like</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Why do I need Dispose()</title><link>http://blogs.msdn.com/smaillet/pages/if-i-m-living-in-a-managed-world-why-do-i-need-dispose.aspx#8690059</link><pubDate>Fri, 04 Jul 2008 20:00:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8690059</guid><dc:creator>Embedded Musings</dc:creator><description>&lt;p&gt;In working with C# myself and with customers I've discovered an area of confusion and hidden bugs. Resource&lt;/p&gt;
</description></item></channel></rss>