.NET Debugging Demos
This is a series of debugging demos aimed to help you get some hands on experience in debugging the most common types of Hang/performance, memory and crash scenarios in .net applications.
The demos are written in ASP.NET which means that you do need IIS and .net framework 2.0 installed on the development machine where you install the demos.
Each new demo will have a set of instructions on how to get started but the lab instructions are deliberately kept very brief in order to give you the most chance to explore on your own. Hints will be available for each demo in case you get stuck.
New demos will be published on http://blogs.msdn.com/Tess as time permits (I am planning to release one new lab per week).
All demos will use the same web site so there is only one application to install for all demos.
Note: These demos will cause high CPU usage, high memory consumption and crashes, so make sure that you are only installing these demos on development machines where no one else will be bothered by the system hanging or the web server crashing.
1. Download the demo site (attached to this post) and unzip the files to a folder on your harddrive. (Rev: just uploaded a new version that shouldn't require 3.5)
2. Set up a new virtual directory in IIS called BuggyBits
3. Browse to the default site http://localhost/BuggyBits/default.htm to make sure that you set up the vdir correctly.
4. Browse to the Company info site http://localhost/BuggyBits/CompanyInformation.aspx to make sure that you can view aspx pages correctly.
5. Download and install the debugging tools for windows from http://www.microsoft.com/whdc/devtools/debugging/default.mspx
6. Run the InternetConnections.reg file by double-clicking it to change the number of outgoing connections you can make to the same site in Internet Explorer (note: any registry modification are done at your own risk, if you feel uncomfortable with this you can view the regfile in notepad and make the changes manually)
7. Install tinyget (comes with the IIS6.0 resource kit http://support.microsoft.com/kb/840671 ) we will be using this for stressing some of the pages in order to produce hangs and memory leaks.
Terminology and tools
Each demo/lab will assume that you are familiar with the following:
.symfix c:\mycache .reload
where c:\mycache is where it will store the local copies of the cached symbols. If you choose to save workspace information when asked in windbg, this symbol path will be saved for the next debugging session.
Some familiarity with the sos commands and windbg is also useful. The following articles may be useful to use as reference material:
Getting started - Part I
Getting started - Part II
This is the first in a series of about 10 labs on .NET debugging. The lab will use a site called BuggyBits,
FYI - This mentions that the code requires .Net 2.0, but I had to install 3.5 to get the Featured Products page to load.
Thanks for pointing that out Pedro,
The actual app doesn't make use of any 3.5 specific stuff so if you want to you can safely remove any using statements for System.Linq and similar and any portions of the web.config that make use of 3.5 dlls. I will try to remove any such references and upload a new version as soon as possible that doesnt require 3.5
I created the sample in 2008 and didnt think about the references to 3.5 that were added by default. Sorry bout that
Where I can find the InternetConnections.reg ?
there is no link in your post
It should be in the zip file.
Earlier this week I published the first .NET Debugging Demos Lab. If you haven't downloaded and tried
It was nice to see that so many people downloaded the demo site already and checked out the lab instructions
I think this will gonna be the seed for a book :)
Hi all, I realize that you probably haven't all had a chance to look at the Crash lab yet, considering
great, i will make it chinese.
TGIF, almost time for the weekend... but before you leave, here is lab 3. Todays debugging puzzle will
Is the zipfile still available??
It seems to can't be downloaded!!
Such a great lab that I can't just let it go!!
The zipfile can't seem to be downloaded !!!
The zip file should still be available and I just tried downloading it a moment ago and then it worked fine so i suspect there might have been a temporary glitch yesterday.
Last week I published a debugging challenge for Lab 5. It was really interesting to see the results and