# .NET Framework → .NET 10 migration & Docker/Linux hosting

> Off Framework, off Windows Server, onto Linux containers — while the system keeps serving traffic.

Source: https://amitkuzi.com/services/framework-to-net10-migration/

The parts that hurt are rarely the language. They are the Windows-only
dependencies, the WCF endpoints, the registry and file-system assumptions, the
COM interop somebody added in 2011, and the deployment that lives in a person's
head. Those get found first, priced, and dealt with one at a time.

I have run this migration on production systems, including converting legacy
CoreWCF services to REST APIs with an AI-assisted conversion rig where the
volume justified building one.

## What you get

- An inventory of every Windows-only dependency, with a decision per item
- WCF and legacy endpoints mapped to their replacements
- A Dockerfile and a Linux hosting setup that your team can operate
- Cutover done in stages, with a way back at every stage