Whew... Mine had broken again - it was only falsely working before. I fixed by adding a web.config into my Views folder so the project knows it's an MVC folder. I copied the one from Nop.Web/Views, then closed and reopened the solution (to force a re-index), and voila! However, now I have other problems the newly enabled intellisense exposed!
This is not only in my project. It is in all projects in pluging folder...
Hi, if so many people are unable to resolve it, and there are so many posts on the internet....please do drop your comment at the Microsoft team and vote to receive assistance. J.
I was also only getting partial intellisense, I didn't notice until I got down to using custom Nop classes. After a whole lot of trial and error, the only way I could get it working is by converting the Class Library project into an MVC project. I voted for the fix on the microsoft site, and also added the workaround there. I edited my project's csproj file with:
1. In <PropertyGroup>, add <ProjectTypeGuids>{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids> 2. Add another import at the bottom: <Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v12.0\WebApplications\Microsoft.WebApplication.targets" Condition="false" />
Let me know if anyone else does this and later runs into issues because of it.