Built on Where it can go Watch for
ASP.NET Web Forms (.aspx pages) Nowhere directly. Web Forms isn't in modern .NET, so it stays on Framework 4.8.1 or gets rebuilt screen by screen in Razor Pages, MVC or Blazor Business rules sitting inside button-click handlers in the code-behind. They have to be pulled out before any page can be rebuilt.
ASP.NET MVC 5 or Web API 2 ASP.NET Core on .NET 10, with controllers and views reworked rather than rewritten Code that reaches for HttpContext.Current or anything in System.Web. Sign-in and permissions get set up again, not copied.
WCF services CoreWCF for the server side, or a REST or gRPC API in its place Who calls it. Other internal apps may talk SOAP to this service and need to keep working on the day it moves.
Windows service or scheduled console app A .NET 10 Worker Service, usually the easiest part to move The account it runs as, and the file shares and folders that account can reach today.
WinForms or WPF desktop app Modern .NET on Windows Third-party control libraries. Each one needs a version built for modern .NET, and some vendors stopped at Framework.
Already on .NET 8 or 9 Retarget to .NET 10, mostly package updates and a full test pass Libraries pinned to an old major version. Those are where the breaking changes hide, not in the runtime itself.