I know "as-is" if you write an MVC app and just import the BlogEngine.Net code it would not work "as-is", there is a lot of work to get Current BE into a workable pure MVC Web application and would require some rewrites, additional code,
and etc to get it working.
The question I was aiming to ask is after all of the "technical" parts are worked out and we have a fully working pure MVC web application version of BlogEngine.net and some how all of the parts that are currently in BE are fully working in the pure
Would there be any need for Webforms as a "framework" or as a "view engine" in the MVC version of BlogEngine.Net?
Trying to see if there are any functions that Webforms provide as a Framework or as a View Engine that I am missing that can't be replaced with MVC and Razor?
As far as I know everything from a Web Form Framework and View Engine can be rewritten to function inside of a MVC Framework using Razor as view engine.
Just wanted to confirm this 100% through, so this can be worked out later on down the line.
I am trying to document and map out exactly what is needed for the process of going from Current BE to a pure MVC web application using only MVC Framework with Razor as the view engine :)
Will also share the documents once it is done :)
Goal is to have an Architecture and code base that can work with the main BlogEngine.Net code base so that they are compatible.