Precompiled Razor View Using RazorGenerator MVC and PreCompiledViewEngine in MVC 4

Step 6: Create a structure as shown below in PreCompiledView to keep the view structure the same as the MVCWebApp project.

Note: I’ve deleted the Index.cshtml from the MVCWebApp project. Kindly refer to the image below:

Step 7: Creating reusable ASP.NET MVC views with the Razor Single File Generator is nearly the same as creating views within an ASP.NET MVC project itself. When you create a folder structure similar to the ~/Views folder convention that ASP.NET MVC expects, the only thing you need to do is associate the views with the Razor Single File Generator by setting each view’s Custom Tool property to RazorGenerator.

Now open up the properties for the Index.cshtml file and set its Custom Tool property to RazorGenerator, also shown in the following image:

Immediately after you specify the Custom Tool property, you should see that the Razor Single File Generator has generated the class Index.generated.cs, grouped underneath Index.cshtml (as shown in figure below).

We are almost done and now press F5 to see how it works.

I’ve set a breakpoint in RazorGeneratorMvcStart.cs to determine the mapping managed by the newly created ViewEngine.

After executing this line, kindly proceed and see that a new View Engine has been added to the existing list to handle the Precompiled View. It’s really awesome to manage Precompiled Views.

Press F5 and see the real output (its same as we have for the same application).

ASP.NET MVC now executes the precompiled Index.cshtml file from the class library, not caring that the file did not exist in its local ~/Views folder. But how did the PrecompiledMvcViewEngine know which view to render

Note: But how did the PrecompiledMvcViewEngine know which view to render? Though it may be surprising, PrecompiledMvcViewEngine still relies on the ASP.NET MVC Views folder convention, using relative file paths to locate the views. However, this is slightly misleading. The PrecompiledMvcViewEngine doesn’t look at physical files; it looks for the System.Web.WebPages.PageVirtualPathAttribute that the Razor Single File Generator adds to every view that it generates that includes the view’s relative file path. The following shows the first few lines of the sample view Index.cshtml that includes that

[System.Web.WebPages.PageVirtualPathAttribute ("~/Views/Home/Index.cshtml")]

public partial class Index : System.Web.Mvc.WebViewPage<dynamic>

Since the virtual path name is relative, whether the ~/Views/Home/Index.cshtml view resides in the ASP.NET MVC application or the class library project, its virtual path is the same. Thus, when the ASP.NET MVC application requests the Index view in the Home controller, the precompiledMvcViewEngine knows to use the precompiled Index.cshtml view registered with the virtual path ~/Views/Home/Index.cshtml

Conclusion