Modernize ASP.NET Web Forms apps and move them to .NET Core
without rewriting everything

DotVVM can be used for incremental modernization of legacy ASP.NET Web Forms applications.

The process of modernization can be scheduled for a period of weeks or months, and the application can be extended with new features and deployed at any time during this period.

Even if the application is more than 10 years old, the Web Forms pages can be replaced one by one with their DotVVM equivalents, and the development of the new features doesn't have to wait until the modernization is completed.

  • Incremental way of migrating away
    from ASP.NET Web Forms
  • The business layer can stay unchanged 1)
  • ASP.NET pages and controls can be rewritten into DotVVM one by one
  • Code-behind files are refactored to MVVM viewmodels
  • The application can be deployed
    at any time during the process
  • After Web Forms are replaced with DotVVM,
    the project can safely move to .NET Core 2)

DotVVM supports both old ASP.NET and new ASP.NET Core stacks, and can run side-by-side with other frameworks like ASP.NET Web Forms.

This migration path allows to install DotVVM in an existing Web Forms application and incrementally replace ASPX pages with DotVVM ones while the application is still working and can be deployed during the migration process. After the Web Forms pages and components are replaced completely, nothing should prevent to just switch the project to .NET Core and get full advantage of the new ASP.NET Core platform.

1) If the business logic is spawned in the code-behind files, the process of refactoring code-behind files into MVVM viewmodels should include moving the business logic to the correct application layer.

2) There might be another dependencies or libraries in your project that are not supported in .NET Core, like WCF or Workflow Foundation. Please review the .NET Core documentation to make sure all components used in the application are supported.