Port .NET Framework apps to modern cross-platform .NET
An agent analyzes an old .NET Framework solution, updates projects and incompatible APIs, and produces a build for testing on Linux.
The use case
Windows-only .NET Framework apps keep licensing and hosting costs high, and porting them is slow because of API changes and old packages. AWS Transform for .NET analyzes the solution, plans the port, updates project files and code, and reports what it could not convert. GitHub Copilot offers similar upgrade help in Visual Studio. The output is a branch that builds on modern .NET. Developers still fix the leftovers, run regression tests, check performance on the new runtime, and plan a staged rollout.
Example workflow
- Connect the source repository
- Run analysis and review the port plan
- Let the agent update projects and code on a branch
- Fix reported leftovers and run regression tests
- Deploy to a test environment before production
Tools
- AWS Transform
- Visual Studio
- GitHub Copilot
Risks and guardrails
- Behavior differences between runtimes may not show in tests
- Third-party packages may lack modern versions
- Keep the old version runnable until the new one is proven
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- AWS: Transform for .NET: aws.amazon.com/transform/windows/net
- AWS Transform MCP Server (official page): github.com/awslabs/mcp/tree/main/src/aws-transform-mcp-server (checked 2026-11-19)