I had this issue after upgrading to VS 2013 Express Preview. Then I noticed there was a line in web.config that was: <add key=”webpages:Version” value=”1.0.0.0″ /> Changed it to the version of system.web.webpages.dll in my bin folder: <add key=”webpages:Version” value=”3.0.0.0″ /> …and the problem went away. (in your case I guess it’s 2.0.0.0.)
I resolved this issue by setting System.Web.Mvc.MvcWebRazorHostFactory, System.Web.Mvc Version to 5.2.0.0 and it worked, finally! Why 5.2.0.0? Same version as NuGet Microsoft ASP.NET project. So, the line in /Views/Web.Config should be: <host factoryType=”System.Web.Mvc.MvcWebRazorHostFactory, System.Web.Mvc, Version=5.2.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35″ />
From Conflicting versions of ASP.NET Web Pages detected: You need to set webpages:Version appSettings with appropriate value. In your case it has to be 2.0.0.0 <appSettings> <add key=”webpages:Version” value=”2.0.0.0″/> </appSettings>
The problem you are having is the query command is taking too long. I believe that the default timeout for a query to execute is 15 seconds. You need to set the CommandTimeout (in seconds) so that it is long enough for the command to complete its execution. The “CommandTimeout” is different than the “Connection … Read more
I had the same problem, but when migrating ASP.NET MVC 3 to ASP.NET MVC 4. This way I got on this topic. I have found a solution to the problem, but its source is different, it is not from WebPages version. I have followed the official guide (so to say) Upgrading an ASP.NET MVC 3 … Read more