Thursday, April 5th, at noon, we’ll be having our second from the last @home webcast, this time focusing on debugging and diagnostics in the cloud. While a lot of what we show is in the context of our @home app… … much of what we’ll be doing is fairly general in nature, especially some of the diagnostics material we’ll be covering this week. From this week’s abstract: In this third webcast episode, we talk about debugging your application. We look at debugging locally and how the emulator works for local development, and we talk about configuring diagnostic data to capture logs and performance counters. For the especially tricky troubleshooting issues, we discuss IntelliTrace, an advanced debugging tool, to gather more information about your application—essentially building a timeline of events that can be examined to quickly find the root of a problem. We also look at remote desktop options for troubleshooting. We’ll talk with you then!
Part 4 of the 5-part series is up on Channel 9. In the previous screencasts, we looked at setting breakpoints and how to work with advanced breakpoints, filters, and working with multiple threads. We also took a quick look at tracepoints. In part 4, we'll look at the watch windows, the immediate window, and Make Object ID command…
The third in the series of debugging tips has been posted to Channel 9(including the player here, too). A quick abstract: In parts 1 and 2, we looked at setting breakpoints, and talked about setting up advanced breakpoints using hit counts and some simple conditions. In part 3, we’ll dive a little deeper into some conditions by writing methods to help debug our application, then look at using the filter breakpoint modifier to debug multithreaded applications. Finally, we’ll take a quick look at tracepoints.
Part 1 was a pretty basic introduction to setting breakpoints. Now it’s time to have a bit more fun! In part 2, I’ll look at using breakpoint modifiers – specifically, using the hit count modifier, and then the condition modifier. The condition modifier can be incredibly powerful – while we can corrupt the state of our application pretty easily (as I’ll demonstrate), it starts to open a whole new world for debugging more efficiently.
Recently, I’ve been doing a number of talks on tips and tricks with the Visual Studio debugger. I thought it would be a good idea to start putting together a series of DevNuggets on these tips – so here is the first! Part 1 is primarily an introduction into setting breakpoints … turns out there are number of ways to set breakpoints other than just clicking in the gutter. This is primarily of interest to entry level developers, but the follow parts will get into some advanced techniques.