Tom Christian's Blog

So I tend to describe a lot of issues here, but we had some really great conversation in our blog chat.  So I thought I would ask for questions from everyone.  Feel free to ask anything you like.  If it is a simple, quick answer, I’ll answer here in this blog posting.  If it is more complex, I’ll create a posting just for your question.

Here is yet another command you may not be aware of.  But it can we really helpful when you are troubleshooting many types of issues with IIS/ASP.NET.

There are multiple ways to capture a dump.  There are some examples discussed in my previous post, HOWTO- Capture a dump on a specific managed exception.  You can just use DebugDiag to capture a dump.  The easiest way in DebugDiag is to just click on the Processes tab, find the process you want to get a dump for:

I am considering creating some videos showing some debugging tips.  My original idea is to create short videos that just some doing some specific things.  So not full debug sessions, but rather specific parts.  So that when you are debugging, you can use these videos to help you troubleshoot and figure out what to do next.

Thanks to everyone that attended the chat we had today on Tess and my pages.  I think it went really well and we are going to continue these in the future and hopefully get to some more topics.

Welcome to the first blog chat for ASP.NET Debugging.  I hope you enjoy this and please let me know your comments on the experience.  I am planning on posting a recap of the conversation (or question and answers) after we are done to the blog so that others can see what was discussed.  If it gets busy and your question doesn't get answered, I will be reviewing the chat and will get an answer posted in the recap.  This chat will last an hour.

So with IIS7, there is a new way to get data out about your web server, using the new appcmd.exe process.

The default stack size of IIS starting with Windows Server 2003 was changed.  Prior to 2003, it was set to 1 MB.  This is also true of the aspnet_wp.exe process that Windows 2000 uses.