ASPX pages: sometimes yes, sometimes no!

I noticed recently with 2.0 release 249 that my aspx pages will sometime be
recognized by R# and sometimes not. I am not sure of what the pattern of
opening/closing etc, that I am using and I can't get it to reproduce. If
anyone else is noticing this and can suggest how to get it to happen/not
happen, I will see if that is my case too.

When it recognizes the page, it seems to work ok, except that any custom
tags that have had their case changed to lower case by VS2003 are being
flagged as unrecognized and I lose my nice clean, green status bar on the
right


6 comments
Comment actions Permalink

Hi,

I have investigated into this, as I have seen it too.

In this page code I am using a 3.part component from telerik, and it parses correct by Resharper:

Untitled Page

If I changes the 'RadTabStrip' tagname to all lowercase 'radtabstrip' Resharper gives an error on that. On the other hand if I keep 'RadTabStrip' and instead change the 'TextBox' tag name to all lowercase 'textbox', there is no error from Resharper. If I change: into Resharper will have lost the reference to the assembly and will suggest to import the namespace. So, the conclusion is that 3.part components names are case sensitive seen from Resharpers point of view, where as the the standard asp controls are not. In all cases, will the page compile and run correct in a browser. Hope this can be fixed in Resharper. /peter "Richard Haber" wrote in message news:e57d04$u44$1@is.intellij.net... >]]>I noticed recently with 2.0 release 249 that my aspx pages will sometime be

recognized by R# and sometimes not. I am not sure of what the pattern of
opening/closing etc, that I am using and I can't get it to reproduce. If
anyone else is noticing this and can suggest how to get it to happen/not
happen, I will see if that is my case too.

When it recognizes the page, it seems to work ok, except that any custom
tags that have had their case changed to lower case by VS2003 are being
flagged as unrecognized and I lose my nice clean, green status bar on the
right

>

Attachment not added (general error): "att1.html"

0
Comment actions Permalink

Peter,

So, the conclusion is that 3.part components names are case sensitive seen from Resharpers point of view, where as the the standard asp controls are not.


You are right, this is a known problem that we don't support case-insensitive names for custom controls. The issue will definitely be fixed in the bugfix update. Hope, the EAP with the fix will appear in a couple of weeks.

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

0
Comment actions Permalink

Hi,

Sounds great !

So I can count on that these 3 errors regarding aspx support in Resharper will be fixed real soon :)

1. Adding a component in design mode don't always trigger a Resharper cache update.
2. Linebreaks inside tags prevents Resharper from parsing the file correctly.
3. The Reharper parsing of aspx in not case-sensitive.

/peter
"Sergey V. Coox (JetBrains)" <qx@intellij.com> wrote in message news:e595eu$l93$1@is.intellij.net...
Peter,

> So, the conclusion is that 3.part components names are case sensitive seen from Resharpers point of view, where as the the standard asp controls are not.

You are right, this is a known problem that we don't support case-insensitive names for custom controls. The issue will definitely be fixed in the bugfix update. Hope, the EAP with the fix will appear in a couple of weeks.

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

0
Comment actions Permalink

Hi,

Ups, item 3 should of cource be that the current parsing is case-sensitive, but you know what I mean :)

/peter
"peter sørensen" <xx.xx@xx.xx> wrote in message news:e596em$rbf$1@is.intellij.net...
Hi,

Sounds great !

So I can count on that these 3 errors regarding aspx support in Resharper will be fixed real soon :)

1. Adding a component in design mode don't always trigger a Resharper cache update.
2. Linebreaks inside tags prevents Resharper from parsing the file correctly.
3. The Reharper parsing of aspx in not case-sensitive.

/peter
"Sergey V. Coox (JetBrains)" <qx@intellij.com> wrote in message news:e595eu$l93$1@is.intellij.net...
Peter,

> So, the conclusion is that 3.part components names are case sensitive seen from Resharpers point of view, where as the the standard asp controls are not.

You are right, this is a known problem that we don't support case-insensitive names for custom controls. The issue will definitely be fixed in the bugfix update. Hope, the EAP with the fix will appear in a couple of weeks.

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

0
Comment actions Permalink

Peter and Sergey,

Thanks for clearing this up for me. It is sometimes comforting to know one is not the only user in the entire world who is experiencing a problem.

Richard
"Sergey V. Coox (JetBrains)" <qx@intellij.com> wrote in message news:e595eu$l93$1@is.intellij.net...
Peter,

> So, the conclusion is that 3.part components names are case sensitive seen from Resharpers point of view, where as the the standard asp controls are not.

You are right, this is a known problem that we don't support case-insensitive names for custom controls. The issue will definitely be fixed in the bugfix update. Hope, the EAP with the fix will appear in a couple of weeks.

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

0
Comment actions Permalink

Peter,

I do promise issues 2 and 3 will be fixed. The first one is rather complicated, we'll do our best.

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

0

Please sign in to leave a comment.