.NET dependency & upgrade analyzer
.NET 8 and .NET 9 lose security support on 10 November 2026, 4 days from today. Paste the contents of your .csproj or packages.config to see which target frameworks and NuGet packages will make a move to .NET 10 harder, and roughly how big the job is.
Paste the contents of a single project file. This runs entirely in your browser: nothing is uploaded, sent or stored. It flags the frameworks and packages that commonly need attention in an upgrade. It is a quick indicator, not a full audit, and it can't see code, configuration or runtime behaviour.
Packages worth a closer look
No frameworks or packages from the known-problem list were found. That's a good sign, but it isn't a clean bill of health: an upgrade can still be held up by code, configuration, custom build steps or packages this tool doesn't track.
The .NET upgrade audit starts from £1,500. It checks every project, package, breaking change and hosting dependency across the whole system and gives you a costed, staged plan. You keep the written report whether or not I do the work.
What it looks for
- Target framework: whether you're on an out-of-support version (.NET 8/9 from 10 November 2026, or .NET 6/7 and older already), on classic .NET Framework, or already current.
- Packages with no direct forward path: classic ASP.NET (
System.Web, old MVC/Web API), OWIN/Katana hosting,BinaryFormatter, and other APIs that need porting rather than updating. - End-of-life or re-licensed packages: for example IdentityServer4 (no longer patched) and libraries that moved to a commercial licence in recent major versions.
- Old-format signals: a
packages.configfile, or legacy Azure and data-access packages that have modern replacements.
For the background, read .NET 8 end of support: what it means and what to do, or take the ten-question readiness check.