Let's do a social engineering experiment. You see, ReSharper has been ignoring pageParserFilter code in asp.net (the thing asp.net MVC and OpenRasta use to enable you to use the C# syntax in your Inherits attribute in asp.net pages) for what feels like forever.
Before the 5.x release, it was still working fine (call it a feature by accident), recognizing the type and enabling full intellisense. Behavior has changed, first by marking everything as an error (in 5.0), and now by compeltley ignoring the base type (5.1). The only reason MVC works is because they special-cased that codebasae, but not OpenRasta's one.
Let's all help JetBrains do the right thing and ask them to re-enable OpenRasta support through a hotfix of their current versions, by voting on this issue: http://youtrack.jetbrains.net/issue/RSRP-92986
In the meantime, you should be able to get by by specifying the old ResourceView`1 syntax in your Inherit clause, or just do like me and don't switch to version 5 just yet.
9 comments:
I've run into this issue outside of OpenRasta (which we aren't currently using) and have been incredibly frustrated with it. We store our controllers/models/views in separate class libraries (the views as embedded resources) that are then loaded into an MVC web app (simliar to MvcContrib's Portable Areas). In ReSharper 4.x IntelliSense worked fine with this setup. As soon as we switched to ReSharper 5.x, no dice.
I contacted ReSharper support about it in early June and receive no communication in return. Can't say I'm terribly impressed with the company right now (which is too bad - I love their products).
I've voted for the issue and left a comment reiterating much of the above. Thanks for bringing this to more people's attention, Sebastien.
@Troy,
Can you tell me who you contacted? Also, please let me know if it's the exact issue Sebastian is talking about or a different one and whether you logged it in http://youtrack.jetbrains.net.
Please feel free to contact me at hadi at jetbrains dot com or via twitter (hhariri)
@Sebastian,
You do recall I said that we'll do our best to resolve this issue right? :) And I think there's some follow-up comments by Sergey.
Thanks.
Hadi - I've forwarded my original email to support to you. Yes it is the same issue as Sebastien has run into, just encountered in a different context.
No I haven't logged it on YouTrack, but I think I logged it on Jira before you switched over. I can't seem to find any of the Jira issues I had logged, so it is difficult for me to say one way or the other at this point...
Hopefully your team is able to find a way to fix what is clearly a regression in ReSharper's functionality.
@Troy,
If it was in JIRA it should be 100% in YouTrack since we imported every single issue. In the future, if you do find an issue, please also consider logging it since even if you email us and we find it's an issue, we'll log ourselves.
Thanks.
If all issues were migrated over then I'm sure you're correct and I never added the issue to Jira. I will certainly make sure to report the issue in the future, since in this particular case it wasn't logged after I sent an email to support.
@Troy,
According to Sergey, apparently your issue is that you're using a regular project instead of a web project and currently ReSharper does not support web features in non-web projects. Per bug entry, he's provided instructions on how to change that and things should work as expected. If not, please let us know.
Thanks
It looks like it's fixed in today's 5.1.1 build: http://confluence.jetbrains.net/display/ReSharper/ReSharper+5.1.1+Bugfix+Builds
Yes, Sergej has been working very quickly to get a fix in for OpenRasta. Will update the post as soon as I've tested the new behavior.
Post a Comment