Your .NET applications lose Microsoft support on November 10, 2026.
Not just the old ones. .NET 8 and .NET 9 both reach end of support that day. After it, no security patches, no bug fixes, no Microsoft support.
Most teams know the date. Almost none have a scoped, costed, sequenced plan — because building that plan takes two weeks of someone's undivided attention, and nobody on an internal team has two spare weeks. That's what I do.
Find your exposure in 90 seconds
Run this at the root of your source tree. It prints every target framework in your codebase, with a count.
Get-ChildItem -Recurse -Filter *.csproj |
Select-String -Pattern '<TargetFrameworks?>(.+?)</' |
ForEach-Object { $_.Matches.Groups[1].Value -split ';' } |
Group-Object | Sort-Object Count -Descending |
Select-Object Count, Name- Projects on net8.0 or net9.0 — the hard deadline. Eleven weeks.
- Projects on net6.0, netcoreapp3.1, or similar — already unsupported.
- Projects on net48 or other .NET Framework versions — a different, bigger problem. Those get rewritten or replaced.
What this actually buys you
Not a document. A position.
- You can answer "how exposed are we?" with a number instead of a shrug — in writing, with a date on it
- You become the person who finally moved the thing everyone has avoided for three years
- Your team ships in minutes instead of remoting into a server on a Friday night
- When the auditor, the cyber-insurance renewal, or the board asks about unsupported software, there is an answer
- And the hosting line on your budget goes down, not up
My guarantee
If the assessment doesn't tell you something you didn't already know, you don't pay. Something material about your own environment. Your judgment, not mine, no argument, any time up to five business days after the readout. You keep the documents either way.
What it costs your team: about four hours, total. Read-only access to your Azure subscription and source control, one hour each with your dev lead and infrastructure lead, and a copy of your current hosting bill.
Why me
Ten years building and running production .NET systems, most recently leading the modernization of a large public institution with several hundred internal repositories, dozens of production databases, and an entire application portfolio on end-of-life frameworks — from audit through live production deployment. I have built this platform and put it into production. Not advised on it. Built it.
Next step
Leave your email and I'll follow up directly — no drip campaign, no spam. I'll ask what you're running, what's already broken, and what happens in your organization on November 11.