ASP.NET MVC - Cannot Resolve Symbol 'Html', 'Model', 'Request'
When I enable solution wide inspection (and sometimes even when I do not) ReSharper returns errors for just about every single one of my View files in my ASP.NET MVC application, saying that the core ViewPage objects Html, Model, Request, and some others are unknown symbols. If I go to the file and select any part of the unknown symbol and simply retype it the error goes away, but it never stays away. I really like being able to use solution-wide inspection to keep an eye on things, but when it contains 74 errors that are false positives then it's pretty much useless. :\
I am currently using the 5.0 EAP client of resharper, but I was also experiencing this issue in 4.5.
Please sign in to leave a comment.
The "inheritInChildApplications" attribute is supported in MVC, but unfortunately ReSharper doesn't like it.
If you add the namespace to the root node of the configuration file (ie: <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">), the "attribute not allowed" errors go away, but ReSharper still ignores any configuration within the <location> tag.
Since this tag is the only way to prevent child applications from inheriting the configuration of the parent application, it seems there's no way to make a working site which R# can analyze; either the child applications try to load the parent configuration and fail at run-time, or R# chokes on the config file. :(
I've a similar problem. Using MVC 3 Framework 4.0 Resharper 6.0
Anyone an Idea?
Martin,
your problem does not actually look similar. But is it reproducible consistently? Does it go away when caches are cleaned?
Have you tried R# 6.1 yet?
Yes you are right, it is not similar ;)
Yes it is reproduceable persistently.
I've followed the steps by cleaning the caches and restart the solution.
But there is no effect.
Now, i will upgrade to 6.1, test it, and let you know the result.
thanks in advance
Martin
Now, I'm happy. I've tested 6.1 EAP and this problems are solved in this version.
How about the License. Can I use my 6.0 aquired license?
thx
Martin
Now, I'm happy. I've tested 6.1 EAP and this problems are solved in this version.
How about the License. Can I use my 6.0 acquired license?
thx
Martin
Sure, your 6.0 license is valid for 6.1.