I've seen this idea a few places now: "Each implementation of a DebuggerVisualizer can be associated with only one type." "Debugger visualizers for different classes must reside in a separate project." And I'm really not sure what to make of it...

I posted in January about a proposed cut of crashdump ( windbg : ".dump /f", now superseded by minidumps) support in Visual Studio 2005. Thanks to everyone who commented - I'm sure you'd like to hear the results... drumroll please... We cut it. Hopefully...

[Update: this feature was cut in the final version of Visual Studio. It's a great idea we may revisit in the future, but our implementation for VS2005 was bad. It caused hangs for some of our users and very confusing error messages for many others .]...

C# Chat: The C# IDE "Expansions, enhanced intellisense, type colorization, refactoring, improved code navigation, metadata as source, Edit and Continue! So many new features, you'll want to make sure you can hit the ground running. Or perhaps you have...

I've received a second response to my call for Debugger Visualizers . And I must say, folks, that this is one sweet visualizer. Brett Johnson 's ASP.NET Control Visualizer is a perfect example of what visualizers can add to your debugging experience....

The first response to my request for debugger visualizers is from Daniel Moth . His little String Encoding Visualizer is great for anyone dealing with string encodings. It could easily become an absolutely essential tool for this kind of development....

Howard Van Rooijen recently emailed me about the XML Debugger Visualizer he's developing, wondering about upcoming changes to the API in Beta2. First let's talk about Howard's visualizer. It looks quite flashy and cool - at least check out the screenshots...

C# Chat: The C# Language "Want to know more about anonymous delegates in C# 2.0, or our design rationale for them? Perhaps you have some great ideas you'd like to share with other C# users or the C# language team. Join the C# team for all that and more...