VS.NET 2003 Annoyance

VS.NET really annoyed me today. When I changed my custom page base class to be abstract, the web forms that inherit from it could only be seen in HTML mode. Their HTML editor leaves a lot to be desired. Maybe I’ll have to figure out how to switch to SciTE automatically when the visual designer croaks.

On the other hand, not using the visual designer does get rid of VS.NET’s annoying habit of trying to create new declarations of web user controls in the web form code-behind when you’ve already got them declared in a custom base page class.

Comments

  1. Dave Sanders says:

    Hey, VS.NET 2005 ain’t much better. If you don’t nest controls properly (like say you put a bunch of stuff in a asp table that’s inside a panel) then the controls just dont show up on the design view.

    I also hate that if you right click on the code and say “View Designer” that it takes you to the designer view, not the html view, and I can’t find a way to change that.

    Plus dozens of other annoyances, usually around things like WYSIWYG. And don’t even get me started on the automated code refactoring. Just know you should NEVER ever change a control name in design mode.

    Gotta go look at SciTE now 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.