Register now or log in to join your professional community.
It depends on what you are trying to achieve, your goal. For example I was working on an application which is necessary to build a theming interface for the it and I was working on LESS and minifying it at run-time so I googled on how to build theming mechanism to support front-end interface for my client.
So one of the reasons on WHY you create your view engine is to be able to get your views from different locations rather than the default view enigne locations ('Views/CONTROLLER/VIEWNAME.cshtml' & 'Views/Shared').
Also one big advantage of creating your view engine, is generalizing your architecture to support plugins in an enterprise solution architecture.
One very rich MVC open-source application that support plugins and theming is Smartstore.net
