ASPX parsing issues with vs 2005

I've not been able to really nail a reproducible case, so I am wondering if anyone else is experiencing this. I see a lot of issues with RS parsing asp.net pages (this is the stock 2005 web site project). Sometimes the page code behind class won't recognize any page controls until I either close and reopen the .aspx a few times or make a trivial change and save the file. Very often dependant user controls not getting parsed is causing the page I am working with to show errors. The biggest problem is that in all cases RS is showing the page as parsed with errors (red square, red dashes) rather than parsing in progress. That means I am either trying to track down non-existent errors or ignoring real ones because I no longer trust RS.

Some of this has to do with RS not being able to parse areas that are perfectly valid in ASP.Net (inside client script blocks for example), but other times its just parsing hickups where after some closing/reopening I can cajole RS to properly parse the page.

I am working on a medium size solution: half-dozen library projects, one website project with 100-150 or so ASPX pages, and one web service project with a dozen pages. Its the web site project that RS is having the most problems with.

Is it a goal for the RS team to address these sorts of issues for 2.0? Do you feel you are close? (doesn't feel that way to me, which is why I am asking the question).

Thanks!
-Michael

2 comments
Comment actions Permalink

Hello michael,

concerning the problem with ReShaper loosing sync with the real text of files
- we're investigating
it, and it definitely should be fixed before the 2.0 release.

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

I've not been able to really nail a reproducible case, so I am
wondering if anyone else is experiencing this. I see a lot of issues
with RS parsing asp.net pages (this is the stock 2005 web site
project). Sometimes the page code behind class won't recognize any
page controls until I either close and reopen the .aspx a few times or
make a trivial change and save the file. Very often dependant user
controls not getting parsed is causing the page I am working with to
show errors. The biggest problem is that in all cases RS is showing
the page as parsed with errors (red square, red dashes) rather than
parsing in progress. That means I am either trying to track down
non-existent errors or ignoring real ones because I no longer trust
RS.

Some of this has to do with RS not being able to parse areas that are
perfectly valid in ASP.Net (inside client script blocks for example),
but other times its just parsing hickups where after some
closing/reopening I can cajole RS to properly parse the page.

I am working on a medium size solution: half-dozen library projects,
one website project with 100-150 or so ASPX pages, and one web service
project with a dozen pages. Its the web site project that RS is having
the most problems with.

Is it a goal for the RS team to address these sorts of issues for 2.0?
Do you feel you are close? (doesn't feel that way to me, which is why
I am asking the question).

Thanks!
-Michael



0
Comment actions Permalink

Thats great to hear, thank you!

-Michael

0

Please sign in to leave a comment.