Closed Circuit Consultants · Las Vegas, NV · remote US
Migrate .NET Framework 4 to .NET 10.
4.0 through 4.8.1. One-week inventory: every project, every WCF contract, every Framework-only package. You keep the map. Then a scoped SOW for the move. Target is .NET 10.
What you buy first
One-week Framework 4 inventory
- 1. Free 30-minute call. Solution list, WCF, who owns prod. No retainer to start.
- 2. One-week inventory you keep. Every csproj still on Framework 4. Every WCF contract. Every package that has no .NET 10 build. Auth, crypto, System.Web risk list. A .NET 10 target map.
- 3. Scoped SOW. The inventory is the proposal. Fixed-price for the move, or from $2,500/month if you want us in the repo after.
Every 4.x version, not only 4.6.2
People search the number they run. We take the whole line. 4.8 is not end of support. It is frozen. Do not wait for a 4.9.
| Version | Microsoft support |
|---|---|
| 4.0, 4.5, 4.5.1 | Ended January 2016 |
| 4.5.2, 4.6, 4.6.1 | Retired 26 April 2022 |
| 4.6.2 | Ends 12 January 2027 |
| 4.7, 4.7.1, 4.7.2 | Follow the Windows they shipped with. Still typed in search. |
| 4.8, 4.8.1 | Still supported as Windows components. Frozen product. |
Who has done this
Sean O'Dea is leading a State of California agency move off .NET Framework 4.6.2. Public target on this page is .NET 10. CISSP, GPEN. Closed Circuit Consultants, Las Vegas. That is a Framework 4 shop, not a greenfield .NET 10 shop.
Questions
Which .NET Framework 4 versions do you migrate?
All of them: 4.0, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, and 4.8.1. The target is .NET 10, not 8 or 9.
Is .NET Framework 4.8 end of support?
No. 4.8 and 4.8.1 still ship with Windows. They are a frozen product. Microsoft's future is .NET 10, not another Framework. 4.6.2 support ends 12 January 2027. 4.0–4.6.1 already ended.
Do you move WCF?
Yes. The inventory lists every WCF contract. The SOW maps them to ASP.NET Core / minimal APIs on .NET 10. We do not pretend System.Web ports itself.