<?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>Nine tips for a healthy &amp;quot;in production&amp;quot; ASP.NET application</title><link>http://blogs.msdn.com/dougste/archive/2006/04/05/nine-tips-for-a-healthy-in-production-asp-net-application.aspx</link><description>The following are based on problems I see people having every day in production ASP.NET systems. 1 . Before you go into production, long before, plan, specify, architect, design, code and test for your application to meet your requirements for performance,</description><dc:language>en-GB</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Nine tips for a healthy &amp;quot;in production&amp;quot; ASP.NET application</title><link>http://blogs.msdn.com/dougste/archive/2006/04/05/nine-tips-for-a-healthy-in-production-asp-net-application.aspx#570319</link><pubDate>Fri, 07 Apr 2006 01:03:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:570319</guid><dc:creator>Ron Shouse</dc:creator><description>Great list. &amp;nbsp;I was wondering on point 3, why you shouldn't have strong named assemblies in the bin directory?</description></item><item><title>re: Nine tips for a healthy &amp;amp;quot;in production&amp;amp;quot; ASP.NET application</title><link>http://blogs.msdn.com/dougste/archive/2006/04/05/nine-tips-for-a-healthy-in-production-asp-net-application.aspx#571673</link><pubDate>Sun, 09 Apr 2006 00:49:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:571673</guid><dc:creator>dougste</dc:creator><description>Hi Ron, the main reason is documented &lt;A href="http://support.microsoft.com/?id=813833"&gt;here&lt;/A&gt;. However I have seen all sorts of hard to diagnose weird behaviour resulting from strong named assemblies being put in the bin folders. My colleague &lt;A HREF="/tess"&gt;Tess &lt;/A&gt;is hoping to blog in more detail on strong named assemblies and ASP.NET sometime soon, Doug.</description></item><item><title>ASP.NET: Check your Web Site today for these common assembly related memory and perf issues</title><link>http://blogs.msdn.com/dougste/archive/2006/04/05/nine-tips-for-a-healthy-in-production-asp-net-application.aspx#575355</link><pubDate>Thu, 13 Apr 2006 01:30:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:575355</guid><dc:creator>If broken it is, fix it you should</dc:creator><description>Recently my colleague Doug wrote a nice post on Nine tips for a healthy &amp;amp;quot;in production&amp;amp;quot; ASP.NET application....</description></item><item><title>Una serie di link sulle performance Asp.Net</title><link>http://blogs.msdn.com/dougste/archive/2006/04/05/nine-tips-for-a-healthy-in-production-asp-net-application.aspx#575650</link><pubDate>Thu, 13 Apr 2006 13:33:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:575650</guid><dc:creator>PhilloPuntoIt</dc:creator><description /></item><item><title>Har du lagt en ASP.NET applikation i produktion?</title><link>http://blogs.msdn.com/dougste/archive/2006/04/05/nine-tips-for-a-healthy-in-production-asp-net-application.aspx#575688</link><pubDate>Thu, 13 Apr 2006 14:57:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:575688</guid><dc:creator>guidmaster´s .NET blog</dc:creator><description>Har du udviklet en ASP.NET applikation? Har du lagt den ud p&amp;amp;#229; din web server? Har du husket at s&amp;amp;#230;tte...</description></item><item><title>Nine tips for a healthy </title><link>http://blogs.msdn.com/dougste/archive/2006/04/05/nine-tips-for-a-healthy-in-production-asp-net-application.aspx#575892</link><pubDate>Thu, 13 Apr 2006 20:52:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:575892</guid><dc:creator>Alistair Laing</dc:creator><description /></item><item><title>ASP.NET Performance Checks</title><link>http://blogs.msdn.com/dougste/archive/2006/04/05/nine-tips-for-a-healthy-in-production-asp-net-application.aspx#576944</link><pubDate>Sat, 15 Apr 2006 21:28:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:576944</guid><dc:creator>Javier G. Lozano</dc:creator><description /></item><item><title>Heie Tips zu ASP.NET</title><link>http://blogs.msdn.com/dougste/archive/2006/04/05/nine-tips-for-a-healthy-in-production-asp-net-application.aspx#589066</link><pubDate>Wed, 03 May 2006 15:06:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:589066</guid><dc:creator>nodomain.cc</dc:creator><description>Man lernt doch nie aus. Hier steht warum es uerst schlecht ist, in der web.config einer ASP.NET-Applikation das Flag &amp;amp;quot;debug&amp;amp;quot; auf &amp;amp;quot;true&amp;amp;quot; zu lassen sobald die Applikation produktiv eingesetzt wird.&lt;br&gt;&lt;br&gt;Weiter finden sich hier Nine tips</description></item><item><title>Nine tips for a healthy &amp;amp;quot;in production&amp;amp;quot; ASP.NET application </title><link>http://blogs.msdn.com/dougste/archive/2006/04/05/nine-tips-for-a-healthy-in-production-asp-net-application.aspx#589758</link><pubDate>Thu, 04 May 2006 11:38:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:589758</guid><dc:creator>Markus' Blog</dc:creator><description>&lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/dougste/archive/2006/04/05/568671.aspx"&gt;http://blogs.msdn.com/dougste/archive/2006/04/05/568671.aspx&lt;/a&gt;</description></item><item><title>Development Links</title><link>http://blogs.msdn.com/dougste/archive/2006/04/05/nine-tips-for-a-healthy-in-production-asp-net-application.aspx#622296</link><pubDate>Thu, 08 Jun 2006 18:33:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:622296</guid><dc:creator>Dave's Place</dc:creator><description /></item><item><title>   Tips for a healthy ASP.NET application in production &amp;raquo; Advanced .NET Debugging</title><link>http://blogs.msdn.com/dougste/archive/2006/04/05/nine-tips-for-a-healthy-in-production-asp-net-application.aspx#1451548</link><pubDate>Thu, 11 Jan 2007 22:22:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1451548</guid><dc:creator>   Tips for a healthy ASP.NET application in production » Advanced .NET Debugging</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://dotnetdebug.net/2006/04/15/tips-for-a-healthy-aspnet-application-in-production/"&gt;http://dotnetdebug.net/2006/04/15/tips-for-a-healthy-aspnet-application-in-production/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>.NET Tips &amp; Tricks </title><link>http://blogs.msdn.com/dougste/archive/2006/04/05/nine-tips-for-a-healthy-in-production-asp-net-application.aspx#3272962</link><pubDate>Wed, 13 Jun 2007 22:10:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3272962</guid><dc:creator>Michael's Coding Den</dc:creator><description>&lt;p&gt;Last update: June 13 , 2007 Document version 0.6 Preface If you have something to add, or want to take&lt;/p&gt;
</description></item></channel></rss>