This is a known issue, and we have recently released a workaround NuGet package for MVC 4: http://nuget.org/packages/Microsoft.AspNet.Mvc.FixedDisplayModes.
The workaround is to simply install this NuGet package to your project. If, however, your application customize the collection of the registered view engines, you should make sure that you reference to
Microsoft.Web.Mvc.FixedRazorViewEngineor
Microsoft.Web.Mvc.FixedWebFormViewEngineinstead of the default view engine implementation.