Keep Your Software Getting Security Fixes
Ignyte Software upgrades business applications that run on .NET versions at or near the end of support, so they keep receiving security fixes. .NET 8 and .NET 9 reach end of support on November 10, 2026. We move ASP.NET Web Forms, WCF, WinForms, and .NET 8 or 9 applications to .NET 10 in stages, while the system stays in use and every cutover has a tested rollback.
What changes
- .NET 8 or .NET 9to.NET 10, supported until November 2028
- ASP.NET Web FormstoBlazor or Razor Pages, same URLs
- WCF servicestoCoreWCF, REST, or gRPC
- WinForms on .NET FrameworktoWinForms on .NET 10, or the web
- One risky cutovertoStaged releases with a tested rollback
- Lexington, KYCentral Kentucky & nationwide
- November 10, 2026End of support for .NET 8 and .NET 9
- Staged and reversibleEvery cutover has a tested rollback
- First conversation is freeWe reply within one business day
Last updated October 21, 2026
Which Dates Apply to You
The November 2026 date does not apply to every .NET application. Start by finding out what yours runs on.
- .NET 8 and .NET 9: support ends on November 10, 2026. After that date, Microsoft releases no more security fixes for them.
- .NET 10: the current long-term support release, supported until November 2028.
- .NET Framework 4.7 to 4.8.1: supported for as long as the Windows version it runs on, with security fixes but no new features. .NET Framework 4.6.2 ends support on January 12, 2027. Web Forms and WCF hosting exist only here, not on modern .NET.
- Older versions: .NET Core 3.1, .NET 5, 6, and 7, and .NET Framework 4.6.1 and earlier, are already out of support.
Upgrade Paths by Technology
Each kind of application has its own path. We pick the smallest change that gets it onto a supported platform.
Usually a contained upgrade. We retarget the projects, update packages, fix what the new version changes, test, and deploy with a tested rollback.
Web Forms does not run on modern .NET. We move the site page by page to Blazor or Razor Pages behind the same URLs, and old addresses redirect so links and search rankings keep working. We moved our own website from Web Forms to .NET 10 and kept its old addresses working.
Modern .NET has no built-in WCF server. For SOAP clients you cannot change, CoreWCF keeps the same contract. For clients you control, REST or gRPC is often simpler. The old and new services run side by side until every client has moved.
WinForms runs on modern .NET, on Windows only. We can retarget the app and keep the screens your team knows, or move screens to the web when people need them outside the office.
Technologies
Start With a Review
The paid step between a free call and a build. The fee is credited toward the build.
For software you already run. You get a scored report on access control, data, backups, security, and how easy the software is to change, a risk list with recommended fixes, three priced options, and a fixed-price offer for the next step. Fee credited toward the build.
For a new build. You get a map of the process, an inventory of the systems and data involved, a risk list, three priced options, and a fixed-price offer for a first version. Fee credited toward the build.
How We Upgrade
The system stays in use the whole time. Users move to the new version only after it has passed testing.
- 1Inventory
List every project, its .NET version, its packages, and the services and databases it talks to. Flag anything with no path to modern .NET.
- 2Stabilize
Put the code in source control, write down the deploy steps, and test the backups by restoring them.
- 3Upgrade in stages
Move shared libraries first, then each application, page, or service, with tests around the behavior that must not change.
- 4Cut over
Deploy each stage with a tested rollback, and compare results against the old version on real data.
- 5Keep it current
A care plan applies security patches and plans the next upgrade before the next end-of-support date arrives.
Related Reading
Legacy .NET modernization without a full rewrite
How to stage a migration and avoid a big-bang rewrite.
Read the guide ServiceLegacy Modernization
When the upgrade is part of a bigger move off an aging system.
See the service ServiceSoftware Rescue & Takeover
When nobody on staff knows how the application works.
See the serviceCommon Questions
No. The November 10, 2026 date applies to .NET 8 and .NET 9. .NET Framework 4.7 through 4.8.1 is supported for as long as the version of Windows it is installed on, and 4.6.2 ends support on January 12, 2027. Supported versions still get security fixes but no new features, and new libraries and tools target modern .NET. So the pressure on .NET Framework apps is slower, but it keeps growing.
No. A .NET 8 or .NET 9 app usually moves to .NET 10 with a retarget and package updates. Web Forms and WCF need more work, because they do not exist on modern .NET, but that work can go one page or one service at a time.
Yes. We upgrade in stages, run the old and new versions side by side where needed, and switch over only after the new version passes testing. Every cutover has a tested rollback.
The application keeps running, but Microsoft stops releasing security fixes for it. Any flaw found after that date stays open.
Usually .NET 10. It is the current long-term support release, supported until November 2028, which gives you the longest runway before the next upgrade.
Start with a Production-Readiness Review. It covers end-of-support risk along with security, backups, and maintainability, and it ends with three priced options and a fixed-price offer. The fee is credited toward the build.
Running .NET 8, .NET 9, or Web Forms?
We reply within one business day, and the first conversation is always free.
Start the Conversation →