growing pains to xhtml

[Carlos]

I am currently in the process of making an existing ASP .Net 1.0 compliant
with 2.0. It has been kind of frustarting. Beginning with making
the existing html tags compliamnt with xhtml. It complains about the casing
of the tags! where is the intellisense to detect it, and fix it? Then, there
is the src of an image that does not find. When I bring the dialog box and
want to point to the source does not even display all the files inside the
directory.!
It also complains about the xlmns tag with the html tag, and the ending of
/> for other tags. In summary, for a working project that wanted to
transition
into 2.0, I got about 500 errors with 300 warnings. Thanks MS..

 

[Andrew Robinson]

You can change the Target Schema back to IE6. This will eliminate most of
your issues.

Tools -> Options -> Text Editor -> HTML -> Validation

 

[Patrice]

Well is this unjustified warnings or is this needed change to be XHTML
compliant ?

You might have prepared this. For example you could keep HTML and fix casing
issues so that you have this issue sorted out for the XHTML upgrade.
Intellisense perhaps fix this as you type. On existing document, you could
use search/replace, etc...

 

[Flip]

I ran into this as well, albeit with very small web apps. One thing that
helped me out is you have a keystroke (CTRL+U I believe) that's the shortcut
to lower case your hightlight strings. Helped me, but again, with a small
number of pages and a few websites.

The other suggestion of the changing the validation type should help you out
too.

All this to say, I too can feel your pain. :< But once you get over it (or
are numbed by it? :>), the IDE, the framework, increased APIs, etc etc etc,
I hope you too will start to enjoy the new environment. And if not, hey,
there's always Eclipse with the C# plugins.....naaaaahhhhhhh not everyone
can afford 4GB dev boxes!!!! :> haha That's what we have for our j2ee dev.
:<

 

[Carlos]

I believe that the casing issues, as many other issues could have been
addressed by the intelligense functionality in the IDE. In fact, it was MS
in
first place who produced automatically those tags with mixed case when
the user was designing the pages in the previous version. So I think it
would be just considerate to take into account that if the IDE detects that
the user by default is working with the XHTML validation, to scan the page
and try to do an optimal tag switch. Hopefully the feature appears in the
first
service pack. While then, the users will be sustaining the pain.

 

[Patrice]

Flip seems to have a great tip (lowercasing selected things). IMO MS avoided
that as precisely having VS.NET "updating" your code previously was not
gthat good. Perhaps hety (or a thrid party) will provide an add-in...

I'll suffer perhaps less when we'll upgrade ;-)

 

[Andrew Robinson]

Carlos,

I am sorry but I disagree with your assertion. I am not aware of any place
that Microsoft has inserted tags that had mismatched cases with either VS
2002 or VS 2003 and certainly not with VS 2005. This is likely something
that you typed and the IDE allowed you two get away with it. You can
continue to do that in VS 2005 if you select one of the less restrictive
validation schemas. Your HTML wasn't compliant when you created it.

People have been hounding MS for a long time to leave existing HTML alone
when pages are opened in Visual Studio and VS 2005 makes a lot of progress
towards this. The validation schemas simply validate, they do not modify
HTML. I wouldn't expect this behavior to change in the future.

I also thing that it is reasonable to leave existing HTML alone. Focus your
time and energies on the HTML in new pages.

 

[Flip]

Thanks for the plug Patrice. :> haha I believe I finished migrating my
(small and modest :>) website last night to 2.0. I just need to install 2.0
on my IIS box to publish it.

re suffer less with upgrade
I'm sure MS will fix many, many things with migrating your older apps to
2.0, just the nature of the beast I think? I tried to avoid moving to 2.0
as long as I could, but I just couldn't resist any longer. haha Hey, I'm
doing java dev at work, talk about unreliable/buggy and flacky environments!
:< So VS2k5 (RC1) is a dream compared to what I'm using at work! :>