Modernize ASP.NET Web Forms apps | DotVVM

We use cookies to analyze our traffic, personalize content and ads, and to provide some social media features. We also share information about your use of our site with our social media, advertising and analytics partners who may combine it with other information that you've provided to them or that they've collected from your use of their services.
We use cookies to analyze our traffic, personalize content and ads, and to provide some social media features. We also share information about your use of our site with our social media, advertising and analytics partners who may combine it with other information that you've provided to them or that they've collected from your use of their services.
Necessary cookies are essential and maintain information based on your activity on our site, like remembering your signed in account, selection of your language, or products added to the shopping cart. The website cannot work properly without these cookies.
We use these cookies to measure, collect, analyse and report how users interact with our sites to better understand their behavior. Thanks to this, we can improve the site and provide better experience. The analytics service is provided by Google Inc.
We use these cookies to measure conversions from our advertisement and banners distributed via Google Ads. This allows us to better target the ads and make them more relevant to you.
We use these cookies to measure conversions from our advertisement and banners distributed via Facebook. This allows us to better target the ads and make them more relevant to you.
We use these cookies to measure, collect, analyse and report how users interact with our sites to better understand their behavior. Thanks to this, we can improve the site and provide better experience. The analytics service is provided by Smartlook.
.NET Framework is going to be supported as long as Windows is. However, it won’t get any new features, and the developers wouldn’t be able to take advantage of the new tools and libraries.
.NET 8+ contains thousands of significant performance improvements. It can be hosted on Linux. The developers are much more productive because of the new tooling, faster compilation, or hot reload experience. They can use the new syntax of C# and new libraries which are faster thanks to countless runtime enhancements.
DotVVM allows incremental in-place modernization of legacy ASP.NET Web Forms applications.With just minimal changes to code base, you can replace all Web Forms pages with their DotVVM equivalents, and then target the newest .NET.
There is no need to build a new app from scratch, deal with single sign-on, session, caching, and sharing data between the two apps.
DotVVM can run in the same app with other ASP.NET frameworks. You can add new features or fix issues while replacing the old pages one by one.
In DotVVM, you can access the data the same way as before. No need to build APIs to access data on the client.
Modernizing is an opportunity for refactoring and cleaning up your code. Thanks to the MVVM pattern, it's easy to cover all pages with tests.
Microsoft recommends setting up a second application along the legacy one, and incremental rewrite of the old pages in the new app. This approach allows making larger changes in the new application but requires more effort. Configuring single sign-on, distributed caching, session, and other infrastructure to be able run two application simultaneously is not trivial.
DotVVM allows you to migrate the pages in-place within the same application. This means much less refactoring and required changes in the code, and lower risk coming from hosting two applications which share data and state.
DotVVM offers a unique way to modernize legacy ASP.NET applications without the need to rewrite everything. It is possible to install DotVVM in the current application and start replacing ASPX pages with their DotVVM equivalents one by one.
The application can be deployed at any point of time during the modernization process. The team doesn't need to replace all the pages in one big release - they can deliver new features while modernizing.
After some time, when all artifacts which depend on ASP.NET Web Forms are replaced, the project can be switched to the latest version of .NET and benefit from all the new features on the platform.
If you use this method, the only files that to be rewritten are ASPX pages, ASCX controls, and their corresponding code behind files. All the business logic, data access, integrations, and other code can remain without significant changes.
The modernization is also an opportunity to clean up and refactor the code-base, and thanks to the MVVM nature of DotVVM, the pages may be covered with integration tests.
DotVVM allows your current team to continuosly improve your existing application and remove the technological debt. After the modernization is complete, the developers will be able to benefit from all new features and enhancements brought by .NET 8+.
We have seen many legacy applications that are difficult or even impossible to rewrite.
It would take years to re-build these applications from scratch using modern frameworks and technologies. The only way to replace such application completely is to hire a new team and wait months until they rediscover and rewrite all business logic, and migrate data to the new system.
In the meantime, a lot of work would have to be done twice because the old application would still need to be maintained and extended with new features.
We can help your team to migrate your legacy .NET app. Your developers can focus on your business requirements, and their work will get much easier after the migration.
It depends on the specific app, but certainly not everything.
First, DotVVM pages have different syntax than ASP.NET Web Forms. Although many components have the same names and similar principles, all ASPX pages and ASCX controls will have to be converted to the DotVVM syntax. We have a tool called ASPX Conve