This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 69%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EN%3C/text%3E%3C/svg%3E)
I had rich experience with classic ASP.NET WebForms engine. But since then I worked on other technologies for many years.
Now it seems there are several engines for building web applications: MVC, Razor and Blazor and maybe I am missing something else.
I have a personal website which was built on the classic/old WebForm engine. Now I want to migrate it to a new engine. Which engine is best for my purpose?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 3%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQG%3C/text%3E%3C/svg%3E)
Hi @Neo ,
There is an article that shows how to upgrade an ASP.NET Framework Web Forms to ASP.NET Core MVC using the Visual Studio .NET Upgrade Assistant and the incremental update approach.
link: https://learn.microsoft.com/en-us/aspnet/core/migration/web_forms?view=aspnetcore-7.0
If you want to convert it to Razor page application, you might need to manual migration. Refer to the following articles to learn the basic information about Razor page, and then convert the web page by yourself:
Hi @Neo,
Choosing between Razor Pages and MVC can be challenging as both have their strengths and weaknesses. If your content is structured and simple, Razor Pages is an ideal choice for pages like login or contact us. It allows you to put code related to a specific page and split the logic into external classes, keeping the controllers clean. On the other hand, MVC is better suited for complex databases and web apps with dynamic server views, REST APIs, and AJAX calls.
If you’re looking to build a decent-sized app, you can use both Razor Pages and MVC together. Use Razor Pages for front-end HTML views and MVC for REST API calls. This way, you get the simplicity of Razor Pages and the power of MVC.
It’s important to remember that there’s no one-size-fits-all solution when it comes to choosing a framework. Consider the fundamental similarities and differences between Razor Pages and MVC in the context of your project before making a decision. Ultimately, the choice between Razor Pages vs. MVC depends on your specific needs and preferences.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Razor pages is the most equivalent to webforms, but is a template engine and no support for the fake events like webforms. Blazor would code more like webforms, but you should review the architecture.
I have a personal website which was built on the classic/old WebForm engine. Now I want to migrate it to a new engine. Which engine is best for my purpose?
The "classic/old WebForm engine" is the BlogEngine.NET? If so, IMO, there is no appropriate candidate to migrate it to new framework in the MVC, Razor Pages and Blazor as you will have to start from scratch to create the Blog.