What is the difference between Portal Engine and MVC in Kentico?
From the technology perspective, Microsoft is continually evolving their primary technology stack, they're moving from ASP.NET Web Forms to ASP.NET MVC (and ASP.NET Core MVC) which is the next evolutionary step for Microsoft technology.
Kentico Portal Engine runs on ASP.NET Web Forms. However, Web Forms is a technology not compatible with the new .NET Core framework. Therefore, everyone running on the Microsoft framework needs to switch to MVC, and, gradually, take the first step towards .NET Core MVC.
Is MVC Going to Last?
ASP.NET MVC is not new hype. It has been around since 2009 and is not just a framework; but also a new way of developing. Its Model-View-Controller approach makes code much easier to develop, maintain, and debug. It is built for the future!
Kentico Portal Engine and MVC Timeline
By the end of 2020, Kentico will drop Portal Engine and use pure MVC web development. Additionally, support for Kentico projects built on Portal Engine will cease by the end of 2022.
Why Is Kentico Moving Toward MVC?
Kentico Portal Engine
The ASP.NET Web Forms framework is slowly becoming obsolete
It is harder to find developer talent willing to use the Web Forms framework
Harder maintenance and upgrades
Hundreds of default web parts natively available out-of-the-box
Web parts can be customized to fit particular projects' needs
Widget selections cannot be natively limited to specific editable areas
The MVC development model is future ready
Easier hiring for developer talent as MVC is a widely used modern development model
Easier maintenance and upgrades
Page Builder’s Drag-and-drop, Widget-based interface with superior UX
Full set of open source components and widgets to be delivered during 2019
Developed MVC Widgets are perfectly tailored for a particular project
MVC Widget selections can be easily limited to specific editable areas