Free tool
Check how ready your .NET Framework project is for .NET 10
Add your project files and see in a minute which NuGet packages and parts of the application block the move from .NET Framework to .NET 10, which packages have known vulnerabilities, and roughly how big the job is.
Your project
Add .csproj, .vbproj or packages.config files, choose the whole solution folder, or paste a file below.
Your files stay in your browser. Only package names and versions are sent to nuget.org to look them up.
What the check looks at
- /The target framework of every project.
- /Every NuGet package: whether its latest version supports .NET 10, whether it is deprecated, and whether your version has a known vulnerability.
- /Known blockers: Web Forms, WCF services, Remoting, Workflow Foundation, Crystal Reports and more.
- /The project format and packages.config, the first steps of every migration.
What it cannot see
- /The check reads project files, not code. APIs such as AppDomain, BinaryFormatter or Remoting inside the code are not visible here.
- /Packages from private feeds are not looked up.
- /For a code-level analysis, use Microsoft’s .NET Upgrade Assistant in Visual Studio. The old .NET Portability Analyzer has been retired.
- /The estimate is indicative, not a quote.
Typical blockers when moving from .NET Framework to .NET 10
- ASP.NET Web Forms
- Web Forms does not exist in .NET 10. The pages have to be rebuilt, usually in Blazor or Razor Pages. This is the biggest part of the job.
- WCF services
- Hosting WCF services is not part of .NET 10. The options are CoreWCF or moving to REST or gRPC.
- ASMX web services
- Old .asmx services do not run on .NET 10. They are rewritten as Web API endpoints or with CoreWCF.
- .NET Remoting
- .NET Remoting is gone in modern .NET. Communication has to move to gRPC, HTTP or a message queue.
- Windows Workflow Foundation
- WF is not supported in .NET 10. The community port CoreWF exists, but workflows usually get rewritten.
- Crystal Reports
- Crystal Reports has no runtime for modern .NET. The reports move to another reporting tool, which is often a project of its own.
- COM+ (Enterprise Services)
- System.EnterpriseServices is not available in .NET 10. That part of the code has to be redesigned.
- ASP.NET MVC
- Controllers and views move to ASP.NET Core MVC with moderate changes. Startup, filters, bundling and authentication are rewritten.
- ASP.NET Web API
- Controllers move to ASP.NET Core with small changes. Routing, filters and authentication are set up again.
- System.Web dependency
- The code uses System.Web (HttpContext, Session, Request), which does not exist in .NET 10. Those parts are adapted to ASP.NET Core.
- ASP.NET SignalR
- The old SignalR is not compatible with ASP.NET Core SignalR. Server and clients are upgraded together.
- ReportViewer and RDLC reports
- The old ReportViewer controls are tied to .NET Framework. RDLC reports can run on .NET 10 with community packages or move to another tool.
- Entity Framework EDMX model
- EF6 runs on .NET 10, but the EDMX designer does not. The model moves to code (Code First) or to EF Core.