At a glance
Legacy sources: .NET Framework 2.0–4.8 · WebForms · WCF · WinForms (legacy) · VB.NET (legacy)
Modern targets: C# .NET 10 (LTS) · Golang · Rust · Read models · Event-sourced core where warranted
Typical timeline: 4 weeks to 6 months depending on scope
Project range: $10,000–$150,000
U.S. delivery: 100% U.S. citizen workforce, U.S.-soil delivery
What to know before you modernize
Which .NET Framework version you have, and what support it carries
Support depends on the exact version, not on the family name. Microsoft's lifecycle page lists .NET Framework 4.8 and 4.8.1 with no end date, because from 4.5.2 onward the framework is a component of Windows and is supported for as long as the Windows version it is installed on. Versions 2.0 and 3.0 ended in July 2011, 4.0 and 4.5 in January 2016, and 4.5.2, 4.6, and 4.6.1 in April 2022. Version 4.6.2 ends on January 13, 2027, and 3.5 SP1 on January 10, 2029. On the modern side, .NET 8 and .NET 9 both have an end-of-support date of November 10, 2026, and .NET 10 is the long-term support release, supported until November 14, 2028. We read the exact target-framework and installed-runtime versions from the project files first, because they decide how urgent the work is.
Legacy .NET Framework 1.0 to 4.7 →
When staying on .NET Framework 4.8 is the right call
An application on 4.8 that runs on a supported Windows Server, has no pressing security finding, and needs no new capability is not in an emergency. Microsoft's own list of reasons to upgrade is short: a .NET version or dependency has reached end of support, a new security or compliance requirement appears, or you hit performance or scalability limits that newer .NET addresses. We would add three practical ones: you need to run on Linux or in containers, you need a library that only targets current .NET, or you cannot hire for the old stack. If none of those applies, a smaller step is often better, such as removing dead dependencies, adding tests, and documenting the system. That keeps the option open without paying for a migration the business does not need yet.
Moving ASP.NET to ASP.NET Core one route at a time
For a large web application, Microsoft recommends an incremental migration, which is the strangler fig pattern applied to ASP.NET. A new ASP.NET Core application is placed in front of the original and uses YARP, the Yet Another Reverse Proxy library, to forward any request it does not yet handle. Routes are then rewritten one at a time and served by the new application. The System.Web adapters package, Microsoft.AspNetCore.SystemWebAdapters, lets shared class libraries keep using HttpContext while they are called from both applications. It also supports sharing authentication, by letting the new application defer to the old one, and sharing session state. The cost is running two applications during the migration, so session, authentication, logging, and caching all need an explicit plan.
Upgrading shared libraries in the right order
Most of the effort in a .NET Framework solution is in the class libraries underneath the web or desktop project, not in the project itself. Microsoft's guidance is to upgrade them in postorder depth-first order: leaf libraries with no internal dependencies first, then the libraries that depend on them, and the main application last. Libraries should target .NET Standard 2.0 where possible, or multi-target .NET Framework and a current .NET release. Before that, the project needs preparation: SDK-style project files, PackageReference instead of packages.config, updated NuGet packages, and compiler warnings about deprecated APIs fixed. Microsoft notes that the dotnet command line does not work for ASP.NET Framework projects, so package updates there are done in Visual Studio. Only the libraries needed by the routes being moved have to be upgraded at each step.
Technologies that do not carry over to modern .NET
Some .NET Framework features have no direct equivalent, and each one needs a decision before the schedule is set. Microsoft lists these as unavailable on .NET 6 and later: creating AppDomains, which throws PlatformNotSupportedException, so isolation moves to separate processes or containers; .NET Remoting, replaced by an HTTP-based service or a library such as StreamJsonRpc; System.EnterpriseServices (COM+); code access security; and Windows Workflow Foundation, for which the community CoreWF project is the suggested alternative. WCF server code can move to CoreWCF, a community port hosted on ASP.NET Core that supports the HTTP and NetTCP transports. It does not support distributed transactions or Message Queuing, so a service built on MSMQ or on transactions that span services needs redesign rather than a port. The assessment lists every such dependency by project.
.NET Core and .NET end of support →
What upgrade tools do and do not do
Tooling shortens the mechanical part of a port. Microsoft now recommends the GitHub Copilot app modernization agent in Visual Studio, which analyzes a solution, writes an upgrade plan, and applies many of the changes, and it describes the older .NET Upgrade Assistant as deprecated and no longer actively developed. These tools can convert project files, adjust package references, and rewrite common API calls. They cannot decide which database access pattern to keep, whether a distributed transaction can be removed, or whether the tests mean anything. For that reason we run the tools inside a plan: characterization tests are written first around the behavior the business relies on, the tool-assisted changes are reviewed as ordinary code, and each step ends with the tests passing on the new runtime before the next one starts.
AI-assisted modernization with Claude Code and Codex →
CQRS and event sourcing, where they fit
A .NET Framework upgrade does not need a new architecture by default. Most of an application stays CRUD: reference data, configuration, and supportive records are read and written in place, and a well-done CRUD model beats a poorly done event store. CQRS (Command Query Responsibility Segregation) and event sourcing are separate decisions, and each is applied inside the bounded context that needs it, never as a whole-system architecture. Where reporting fights the transactional schema, a read model or a reporting database is usually the honest answer. Where audit trails and collaboration matter, the core of that context can be event-sourced: business events such as an order being cancelled, with its reason, are recorded as they happen rather than overwritten. Neither pattern requires microservices or the cloud, and neither is chosen for raw performance. The recommendation is matched to your actual complexity, not CQRS-by-default.
Event sourcing for existing .NET systems →
Our Modernization Process
Our modernization begins with a comprehensive analysis of your existing .NET applications. We evaluate the architecture to identify areas for improvement, then migrate to C# .NET 10, Go, or Rust. Where reporting needs it, we add read models or a reporting database. Where audit trails and collaboration matter, we event-source the one bounded context that needs history; everything else stays a plain, well-tested CRUD model. Cross-platform compatibility across Mac OS X, Linux, and Windows is guaranteed, ensuring your applications are future-ready and optimized for modern cloud environments.
What an event-sourced core actually buys
Where a bounded context is event-sourced, the gains are specific: a record of what happened in business terms, with the reason it happened; answers to what was true on a given date; projections that feed reports and analytics without touching the write side; and a model that can be tested against the rules the business states for informed decision-making. They also reduce operational costs through optimized resource utilization.
Future-Ready by Design
Beyond the technical refactor, we prepare your systems for the future: faster, more responsive user experiences; continuous deployment and agile development practices; a deployment shape chosen for your operations, monolith or services, rather than by default; audit trails where compliance requires them; and a scalable foundation ready for further innovation. The result is an application your team can evolve confidently for the next decade.
Start with an assessment for a .NET Framework codebase
For a .NET Framework codebase the assessment inventories the things that decide the path: the target framework of every project, the NuGet and assembly dependencies with their current support status, the web stack in use (WebForms, MVC, Web API, WCF), reliance on System.Web, AppDomains, Remoting, COM+, and Workflow Foundation, the data-access layer and database schema, Windows-only dependencies such as the registry, COM interop, and Windows services, configuration and deployment shape, and whatever automated test coverage exists. Everything is read from source, project files, and configuration; nothing is run and nothing in production is touched. The result is a written recommendation covering whether to stay, upgrade in place, or migrate incrementally, with the library order attached. The fee is quoted after the free 1-hour consultation and creditable toward a subsequent modernization project.
Deliverables
- Migration to C# .NET Core / .NET 8+, Go, or Rust
- Read models where reporting needs them
- Event-sourced core where history matters
- Cross-platform build (macOS, Linux, Windows)
- Cloud-native deployment on AWS or Azure
Common questions
Is .NET Framework 4.8 still supported?
Yes. Microsoft lists .NET Framework 4.8 and 4.8.1 as active with no fixed end date. Since version 4.5.2 the framework has been a component of Windows, so each release is supported for as long as the Windows version it runs on. Older versions are not covered: 4.5.2, 4.6, and 4.6.1 ended in April 2022, and 4.6.2 ends on January 13, 2027.
Which .NET version should I migrate to in 2026?
Target .NET 10, the current long-term support release, which Microsoft supports until November 14, 2028. .NET 8 and .NET 9 both have an end-of-support date of November 10, 2026, so they are poor targets for new work.
Can I upgrade from .NET Framework to .NET without rewriting the application?
Usually yes for business logic and data access, which port with project and package changes. The parts that need real work are the technologies modern .NET dropped: AppDomains, Remoting, COM+, Workflow Foundation, and the ASP.NET System.Web pipeline. A large web application can move one route at a time behind a proxy instead of being rewritten in one step.
What happens to WCF services when moving to modern .NET?
WCF server code does not run on modern .NET as is. CoreWCF, a community port hosted on ASP.NET Core, supports HTTP and NetTCP bindings and most common security modes. It does not support distributed transactions or Message Queuing. Services that depend on those need redesign, and services with few clients may be better replaced by plain HTTP APIs.
How do I migrate a large ASP.NET application incrementally?
Put a new ASP.NET Core application in front of the old one and have it proxy unhandled requests to it using YARP. Move routes one at a time. Use the Microsoft.AspNetCore.SystemWebAdapters package so shared libraries can keep using HttpContext, and configure shared authentication and session where the application needs them. Upgrade only the libraries each moved route depends on.
Do the Upgrade Assistant or AI tools do the migration for me?
They do the mechanical part. Microsoft deprecated the .NET Upgrade Assistant in favor of the GitHub Copilot app modernization agent, which plans and applies many changes. Neither can judge whether tests are meaningful, whether a distributed transaction can be removed, or which behavior the business depends on, so the output still needs review and a test suite around it.
How long does a .NET Framework modernization take, and what does it cost?
The bands on this page apply: 4 weeks to 6 months depending on scope, and $10,000–$150,000. A small library or service upgrade sits at the low end, and a large multi-project web application at the high end. The price and schedule are fixed after the Legacy Software Assessment, whose fee is quoted after the free 1-hour consultation and creditable toward a subsequent modernization project.
Sources
- Microsoft .NET support policy: .NET 8, 9, 10 support types and end-of-support dates; .NET 11 RC status
- Microsoft .NET Framework lifecycle: End dates for .NET Framework 2.0 through 4.6.2 and 3.5 SP1; 4.8/4.8.1 have no end date listed
- .NET Framework support policy: 4.8 and 4.8.1 supported as a Windows component for the life of the host Windows version
- Migrate from ASP.NET Framework to ASP.NET Core: Incremental migration as strangler fig; reasons migration is hard
- Get started with incremental ASP.NET to ASP.NET Core migration: YARP proxy, System.Web adapters, remote authentication and session, postorder library upgrades, SDK-style projects, dotnet CLI limitation
- Upgrade .NET apps overview: When to upgrade; Upgrade Assistant deprecated in favor of GitHub Copilot app modernization
- .NET Framework technologies unavailable on .NET 6+: AppDomains, Remoting, CAS, EnterpriseServices, Workflow Foundation unavailable; CoreWCF and CoreWF alternatives
- CoreWCF 1.0 released: CoreWCF supported transports and bindings; no distributed transactions or Message Queuing
Not sure where to start?
Start with a fixed-scope Legacy Software Assessment: a read-only review of your application’s source, database, configuration, logs, and architecture, ending in findings with evidence and a written recommendation. Quoted after the free 1-hour consultation; creditable toward a subsequent modernization project.