ASP.NET: Check your Web Site today for these common assembly related memory and perf issues

1 minute read

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 you how you can identify them in a memory dump.

As most of you know I like to go into great detail about thingsJ so to make it a bit more manageable I have divided my posts up into 3 different parts (one per statement that Doug makes in his post).

Don’t wait tomorrow to get your application “health-checked” go out there and grab some hang dumps today…