VS 2005 HTML editor is cool

OK I know some people can say I have a constant bad attitude regarding Microsoft products, but hey I like their products and I like also to say when something goes right or wrong.
Here I want to say bravo for the HTML editor in VS 2005. It's really a great job, no more mess with my code reformatted.
One thing I really enjoy is the fact I can collapse any nested div or table element when I am writing my code. It's make the code much more readable and because I am now moving away more and more from the table and use more CSS and div tags. I finally disabled the HTML intellisense validation because I disagree with some of the rules, it could be nice to have some granularity on the level of error the tool report or not. Actually it's just on or off.
After one year of tests on the different betas, I finally start to write some real code. As I say before, I don't use really the migration tool, I prefer to start from a clean project and copy and paste what I need. I know it's a slow process, but I am quite sure its a winning situation in the long term. I hope also very soon to implement the new stuff like master pages, or web parts.

 

4 Comments

  • So sorry you have had so much trouble. I have powered along for the last 3 days converting the biggest project we have (a few hundred pages) and about 20 web services.



    It took about a day to get it working again after running through the wizard (I was expecting much worse). I have spent the last two days moving from our old custom page layout solution to MasterPages; Converting from our internal menu generation system to the standard sitemap system by writing a provider; Converted from our own LoginView control to the standard control; etc, etc. So I am amazed how much progress has been made in 3 days.



    Best part....I estimate the project has already shrunk by 30-40% in size *already*, I expect it to be under half the size by the end of the week!!!!



    WOW!



  • Daniel I don't qualify as cranky! I just express the frustration when something goes wrong, and yes many things are broken with VS 2005 regarding compatibility for example. I don't criticize anything about NEW stuff, but I expect from a BIG company like Microsoft the best. After all they are supposed to have the best developers, so why not claiming for quality?

  • BTW Paschal, my strategy was to ensure all our major apps would run on the V2 runtime as compiled 1.1 apps....That is my starting point was to leave evertying as compiled V1.1 apps, but running under the V2 runtime. Everything worked perfectly apart from a few changed I needed to make to web.config. Plus there was a stupid issue I had (bad programming) where some fields appeared on our web forms in a different order (not a breaking bug - just frustrating)...That was because the order of members returned via reflection has changed under the V2 runtime. It was a stupid mistake of mine, because Microsoft has said since V1.0 of the framework that you cannot rely on the order of members via reflection...Also even MONO uses a different reflection member order than .NET....So it was kinda expected. Anyway...that was not a biggy and did not break anything, but I fixed it for consistency.



    Thus the apps have been running for 3 weeks now in production as 1.1 compiled apps on the 2.0 runtime. Everything has gone perfectly!



    Over the last 1-2 weeks we have been running through the conversion wizards and starting to migrate to out of the box V2 features.



    Seriously...I have not had this much fun for years....I love how clean our codebase is going to look on top of ASP.NET 2

  • David, good point but how many developers work with you? In my case I am alone and hard to find the required time to do everything. One problem I have actually is to have .Text running under 2.0 framework. No idea exactly why yet.

Comments have been disabled for this content.