In Visual Studio.Net, the debugging environment has become vastly superior to anything previously available. Developers migrating from other platforms to .NET often revel in the greatly superior debugger support we have in .NET, compared to what they have to work with in other environments. Have you ever wondered why your .NET application is not responding? Or why it’s intermittently consuming high CPU? Or crashing? When things go wrong you need to think low level, using the proper knowledge and tools to investigate the internals of your application. Bugs suck and debugging is hard! Did you take a class on debugging in college? Of course not. You’ve had to learn debugging by trial and error, with lots of emphasis on the error. Another question: have you read the Microsoft Visual Studio debugger documentation? Again, doubtful. According to the research, most developers spend 50% of their time debugging, but you’re doing it with your hands tied behind your back. Watch these videos and learn the tricks that will make your coworkers say “Wow! How’d you do that?” You’ll learn new techniques of programming the debugger to stop exactly when your bug occurs. You’ll see how to view your data in ways you never thought possible so you can see what you need to see and spend less time guessing. You’ll learn many undocumented techniques for maximizing your usage so you’re never sitting there staring at the computer saying “what do I do now?” You’ll also see the brand new capabilities in Microsoft Visual Studio 2010 such as IntelliTrace, the key feature of Visual Studio 2010, that will forever change the way you approach debugging and problem solving.