<?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>ASP.NET Tips: Debugger command you may not know about – finddebugmodules</title><link>http://blogs.msdn.com/tom/archive/2008/04/01/asp-net-tips-debugger-command-you-may-not-know-about-finddebugmodules.aspx</link><description>So there are a couple different things that can affect performance of your ASP.NET application.&amp;#160; One of them is if you are running with debug builds of your files.&amp;#160; This is where this command comes in.&amp;#160; When run, it will tell you any modules</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>ASP.NET Debugging : ASP.NET Tips: Debugger command you may not know about ??? finddebugmodules</title><link>http://blogs.msdn.com/tom/archive/2008/04/01/asp-net-tips-debugger-command-you-may-not-know-about-finddebugmodules.aspx#8349080</link><pubDate>Wed, 02 Apr 2008 01:08:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8349080</guid><dc:creator>ASP.NET Debugging : ASP.NET Tips: Debugger command you may not know about ??? finddebugmodules</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/tom/archive/2008/04/01/asp-net-tips-debugger-command-you-may-not-know-about-finddebugmodules.aspx"&gt;http://blogs.msdn.com/tom/archive/2008/04/01/asp-net-tips-debugger-command-you-may-not-know-about-finddebugmodules.aspx&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: ASP.NET Tips: Debugger command you may not know about – finddebugmodules</title><link>http://blogs.msdn.com/tom/archive/2008/04/01/asp-net-tips-debugger-command-you-may-not-know-about-finddebugmodules.aspx#8416281</link><pubDate>Tue, 22 Apr 2008 12:13:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8416281</guid><dc:creator>Greg Young</dc:creator><description>&lt;p&gt;I disagree ... greatly ...&lt;/p&gt;
&lt;p&gt;You still want to BUILD with pdbs in case you need to use them later (memory dumps etc) you just don't want to DEPLOY pdbs with your application.&lt;/p&gt;</description></item><item><title>re: ASP.NET Tips: Debugger command you may not know about – finddebugmodules</title><link>http://blogs.msdn.com/tom/archive/2008/04/01/asp-net-tips-debugger-command-you-may-not-know-about-finddebugmodules.aspx#8416369</link><pubDate>Tue, 22 Apr 2008 13:55:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8416369</guid><dc:creator>Tom</dc:creator><description>&lt;p&gt;Greg,&lt;/p&gt;
&lt;p&gt;You bring up a good point. &amp;nbsp;Which is what do you use pdb's for? &amp;nbsp;With managed code, the only reason to have them is if you plan on debugging the application live with Visual Studio. &amp;nbsp;If you are going to look at dumps and use Windbg and other debuggers like that, they don't use pdb's at all. &amp;nbsp;So basically, if you build them, you are putting in the hooks into the dll which are not needed. &amp;nbsp;And with a managed assembly, that actually takes up more memory and causes the files to be bloated. &amp;nbsp;Not just the dll on your drive, but the compiled assembly in memory.&lt;/p&gt;
</description></item><item><title>SOS: Upcoming release has a few new commands – ported from 1.x</title><link>http://blogs.msdn.com/tom/archive/2008/04/01/asp-net-tips-debugger-command-you-may-not-know-about-finddebugmodules.aspx#8618033</link><pubDate>Wed, 18 Jun 2008 22:46:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8618033</guid><dc:creator>ASP.NET Debugging</dc:creator><description>&lt;p&gt;These are not a new command in some regards as they were added to the 1.x version of SOS that ships with&lt;/p&gt;
</description></item></channel></rss>