To consume precompiled views from your Mvc application, you would need to install the RazorGenerator.Mvc package.

Install-Package RazorGenerator.Mvc

How it works

Views generated by the precompiled views contain a PageVirtualPath attribute that records the VirtualPath they correspond to. These values are constructed from the relative paths of the cshtml files under the Views directory.
The package adds a pre-application start hook via the type RazorGeneratorMvcStart to include a ViewEngine to the Mvc's list of engines.

var engine = new PrecompiledMvcEngine(typeof(RazorGeneratorMvcStart).Assembly) 
{
    UsePhysicalViewsIfNewer = HttpContext.Current.Request.IsLocal
};

ViewEngines.Engines.Insert(0, engine);


Configuring the PrecompiledMvcEngine


ViewEngines.Engines.Add(engine);


    // StartPage lookups are done by WebPages. 
VirtualPathFactoryManager.RegisterVirtualPathFactory(engine);


Unlike the ViewEngine scenario, we choose to do the opposite with Layout and ViewStart files: if the path of a _ViewStart file or a Layout file exists both in your precompiled assembly and your Mvc application, we'll choose the one in your Mvc application.

You can change this behavior by setting the PreemptPhysicalFiles to true on your engine:

engine.PreemptPhysicalFiles = true;


UsePhysicalViewsIfNewer = HttpContext.Current.Request.IsLocal