Re: growing pains to xhtml

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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 ;-)

--
Patrice

"Carlos" <ch_sanin@xxxxxxxxx> a écrit dans le message de
news:OPxzTZh6FHA.2676@xxxxxxxxxxxxxxxxxxxxxxx
> 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" <nobody@xxxxxxxxxxx> wrote in message
> news:%23pVIl7g6FHA.2552@xxxxxxxxxxxxxxxxxxxxxxx
> > 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...
> >
> > --
> > Patrice
> >
> > "Carlos" <ch_sanin@xxxxxxxxx> a écrit dans le message de
> > news:%23uh3z%23f6FHA.1020@xxxxxxxxxxxxxxxxxxxxxxx
> >> 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..
> >>
> >>
> >
> >
>
>


.

Relevant Pages