i just found out a bug on visual inheritance concerning the new controls in .NET 2.0. Basically it says that if you have an inherited control (non-private), designer won't allow you to "design it" in the child form (they're locked). more info here .

an officemate of mine got this problem wherein he had specified already the mapping xml files for nhibernate but when he tries to debug it, it was not able to load the said mapping files. turns out he found a bug in vs 2003 that i should have found out months ago. visual studio 2003 does not detect changes...

One innovation I love most with with Visual Studio is their AutoHide windows. I always configure every window (server explorer, debug windows, etc.) to be AutoHide to maximize my code view (eventhough I have a 1280 x 1024 resolution at font size 8). The only problem with the said feature is its bug....

How come Visual Studio intellisense could not resolve shadowed/newed functions, they are still showing the “shadowed” functions.

I always use the "Pending Checkins" window once in a while so I've assigned a shortcut for it. One feature that I would want with VSS and VS integration is the ability to browse the code sheet of an item from the said window. Anyways, checkout the bug that I encountered with the said window...

Last time, I reported a bug on the ToolBar control of Windows Forms which I have discovered upon a query of an officemate. I just saw that there is an update on my reported bug as Won’t Fix due to a breaking change, :p.

Have you tried doing a nested switch statements in Visual Studio. I have tried this and VS is somewhat altering the proper indents. I couldn’t find any flaw on using nested switch statements but the behavior is intriguing. Below are some screenshots:

An officemate of mine could not disable the DropDownArrows for the DropDownButton style ToolBarButton. After trying it out and using Reflector, I found out that the default value for the DropDownArrows property of the .NET ToolBar is not properly configured. The DefaultValue of the said property is FALSE...

Create a form with anchored controls. (Not just the default Top | Left) Resize the form Hit Undo (Ctrl-Z), voila! The Undo feature at design time is handled by the Windows Forms Designer and the said functionality is one of the complex implementations in .NET that I am still unfamiliar with up to this...