here are some list of the behaviors that i hate with Visual Studio 2003. I hope most of them are fixed with the 2005 version. Crashing while attempting to attach to a process i started experiencing this back in my previous company and once in a while i experience it, until now i haven't got any clue...

one reason is because it is so powerful that a developer can even use it to modify the underlying private field of a readonly property. i mean come on, if you hit this roadblock, there's a problem in your design. in my opinion, reflection is not designed to be used this way.

visual studio .net comes with the #region and #endregion directives to be able to collapse code sections using the IDE. by default, the generated code (i.e. InitializeComponent method block) which is used by winform and webform designer to recreate the forms at design time are enclosed in this block...

I got tired of seeing a common property of our controls (since it is part of an interface) and this week, I got fed up and can’t take it anymore seeing them. AlignmentInContainer You might suggest ContainerAlignment but layout properties obviously relates the control to its immediate parent container...