If broken it is, fix it you should

For a long time all my case studies have been on 1.1. it’s time to venture out in 2.0 land and look at what may seem like a 2.0 specific issue. I say “may seem” because this case study will only directly crash if you are using 2.0, but as you’ll learn Read More...

Statement “Ensure that the debug="false" on the <compilation> element in the web.config file of each and every ASP.NET application on the server. The default during development is "true" and it is a common mistake to allow this development time Read More...

Statement “In ASP.NET 1.1, do not deploy strong named assemblies to the BIN directory (i.e. if they are strong named make sure you DO put them in the GAC).” What problems do storing strong named assemblies in the bin directories cause? In ASP.NET 1.1, Read More...

Statement “Wherever possible strong name and install to the global assembly cache (GAC) any assemblies that are used by more than one ASP.NET application. This will reduce memory consumption.” What problems do storing common assemblies in the bin directories Read More...

Recently my colleague Doug wrote a nice post on Nine tips for a healthy "in production" ASP.NET application . I have been planning to post about some of these for a while, so I decided to steal some of his points and expand a bit on them, and also show Read More...