Scott Hanselman

DNRTV Screencast - ASP.NET Debugging and Tracing Part 2

August 22, '07 Comments [2] Posted in ASP.NET | Screencasts | Speaking
Sponsored By

Last week Carl and I did another episode of DNRTV. We picked up exactly where we left off last time on ASP.NET Debugging and Tracing. So, I guess this ASP.NET Debugging and Tracing Part 2

As with all my DNRTV episodes rather than planning Carl and I just start talking and see what happens. It seems more genuine that way, to me. We screw around with Symbols and Process Explorer in this episode.

We also look around the ASP.NET Temporary files and take a look at the assemblies that are generated from your ASPX files, then we add a few string literals and see where in the generated code (and control tree) they show up. All in all, I thought it was a pretty decent show.

It's 36 minutes long with a 3 minute advertisement in the middle. I hope you enjoy it.

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. I am a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Sponsored By
Hosting By
Dedicated Windows Server Hosting by ORCS Web
Wednesday, August 22, 2007 8:51:08 AM UTC
Thanks Scott. You might want to change your bio on dnrtv, though!
Andrew
Wednesday, August 22, 2007 2:32:18 PM UTC
I'd like to put out my vote on continuing this series by digging into WinDbg (i.e. the SOS externsion, etc) and other lower level debugging techniques like you and Carl hinted at. Luckily, we don't have to get into WinDbg very often, but it is really one of those tools that would make so much more sense if we could WATCH someone using it instead of just reading posts. Following Tess's blog posts on WinDbg can be pretty tough without a little more background on the tool.

And while I'm talking about SOS, where in the world is an updated version of the SOS extension for .NET 2.0? The 1.1 extension has been updated left and right, but the 2.0 one hasn't been touched since it has been released (AFAIK).
Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.