I started this blog 2.5 years ago today, mostly because I felt that the same types of issues came up over and over and over in our support cases. I figured that if I started writing about them, a lot of people would be able to resolve them on their own, or even better avoid them in the first place.
A lot of water passed under the bridge since then, but looking back at some of those earlier posts they are still very applicable today, and they still seem to continue to get a lot of hits. Here is a list of the 21 most popular ones...
In 2.5 more years I'll post the answer to the meaning of life, the universe and everything:)
and..., while I'm on the topic... what would you like to see more of in the future?
PingBack from http://ramsonit.wordpress.com/2008/05/21/21-great-blog-posts-related-on-net-memory-management/
You really had a lot of very impressive posts on topics of debugging. Compared with a lot of books related to debugging, your example-based approach is easier to follow and understand.
Thanks for all the hard work.
ASP.NET A New Tutorial Series on Master Pages [Via: Scott Mitchell ] Using parent page properties in...
Isn't the answer to the meaning of life, the universe and everything "42"? I think someone might have beaten you to it :)
exactly:) 21 posts after 2.5 years and 42 posts after 5 years:)
Makes sense. I'll put that on my calendar right now :)
I would like to see more tutorials targeted for beginners. Sort of "introduction to debugging" type posts.
As a part-time programmer, I want to thank you for your continual updates. They have saved me much time and aggravation.
I've just finished writing up an e-mail for some new people in my team about starting Debugging and the
i want to see a post on how debugging can unravel the meaning of life :)
I was looking at you http://blogs.msdn.com/tess/archive/2008/02/27/net-debugging-demos-lab-4-high-cpu-hang-review.aspx article about high cpu and garbage collection. I was hoping that this was the problem with my application but after analyzing the dump it did not point to gargbage collection.
Is there anything else I can look at in the dump to determine why my application has cpu spike every 45 minutes.
When the .NET Framework was first released, many developers believed the introduction of the garbage
This is a great site for debugging