XHTML validation warnings

Hello Paul,

are you sure that it is ReSharper that adds those warnings? It's quite strange
for a ReSharper warning to not appear on the error bar, and also I'am not
aware of such a functionality which is also strange. Try to disable ReSharper
and check
if the warnings persist.


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

When browsing *.aspx files, I notice that Resharper adds some XHTML
validation warnings. This is awesome.

However I have a few issues with the current implementation:

1) They're marked with a red wavy underline, which shouts out "error"
to me, when it's not really an error at this point (it compiles fine
now, it just doesn't meet conventions and standards).

2) There's no indication in the error bar, so that it's easy to see
them all at a glance ... you actually have to scroll through the file
looking for the non-conforming code by scanning for red wavy
underlines.

3) There are no "hot-fixes" or "Quick-fixes" available, which is
especially annoying when the fix is very mechanical and could easily
be handled by Resharper itself (things like uppercase tag names, or
even missing attributes). It would be especially nice if there were
some batch updates possible (like just go ahead and fix all the
uppercase tag names, as that requires no user intervention or brains).

I would love to see this feature expanded upon and fleshed out! We
have a ton of these files, and Resharper could potentially make the
process of making these files conformant much, much easier.

Paul Bradshaw wrote:

When browsing *.aspx files, I notice that Resharper adds some XHTML
validation warnings. This is awesome.

However I have a few issues with the current implementation:

1) They're marked with a red wavy underline, which shouts out "error" to me,
when it's not really an error at this point (it compiles fine now, it just
doesn't meet conventions and standards).

2) There's no indication in the error bar, so that it's easy to see them all
at a glance ... you actually have to scroll through the file looking for the
non-conforming code by scanning for red wavy underlines.

3) There are no "hot-fixes" or "Quick-fixes" available, which is especially
annoying when the fix is very mechanical and could easily be handled by
Resharper itself (things like uppercase tag names, or even missing
attributes). It would be especially nice if there were some batch updates
possible (like just go ahead and fix all the uppercase tag names, as that
requires no user intervention or brains).

I would love to see this feature expanded upon and fleshed out! We have a
ton of these files, and Resharper could potentially make the process of
making these files conformant much, much easier.

This is functionality of VS.NET 2005...

--
Matt Berther
http://www.mattberther.com

Paul,

That's not us, this is VS2005 functionality.

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Ah, well, then take this as a suggestion to enhance existing VS2005
functionality then :)


"Sergey V. Coox (JetBrains)" <qx@intellij.com> wrote in message
news:duoof5$ge4$1@is.intellij.net...

Paul,

>

That's not us, this is VS2005 functionality.

>

--
Sergey V. Coox
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"