<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>MSCOM OPS March Debug Madness…3rd Session Q &amp;amp;amp; A Dignosing Memory Leaks in ASP.NET Applications</title><link>http://blogs.technet.com/mscom/archive/2006/03/31/mscom-ops-march-debug-madness-3rd-session-q-amp-a-dignosing-memory-leaks-in-asp-net-applications.aspx</link><description>Wednesday’s topic was “ Diagnosing Memory Leaks in ASP.NET Applications ” presented by Jim Dobbin, a Sr. Systems Engineer on the MSCOM OPS Debugging Team. As this week progressed we continued to be impressed by the level of the questions asked. Here are</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator></channel></rss>