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 on the cause of this. as a result (to be safe) i attach only when my cpu process is low.
- Dumb Designer serializer
your eventhandlers are sometimes swallowed by the designer so you'll notice that the InitializeComponent method block is slowly decreasing in lines and one morning, the button handlers are not working. also, when you open the aspx files, the designer scrambles the page directives and it's marking the page as modified.
- Designer refresh
sometimes you just have to toggle between code and design view to see your changes or for the designer to regenerate the correct protected asp.net controls in the code-behind (user controls are manually added)
- Solution Explorer toolbar buttons not refreshing
i've posted a workaround about this before here.
- VS is not notified when resx files are the ones who are changed
this happens when you have changed the localized string or your nhibernate mappings but yet your changes are not persisted on your latest build. you have to do a rebuild.
- Shadowed members are still shown in intellisense
good thing i use resharper.
- No prompt/confirmation for moving files
man it's sick when you accidentally moved a file/folder from one project to another, good thing we have version control these days.
Posted
06-27-2006 10:35 PM
by
jokiz