Doing so would be mean and very unfriendly.NET 6 should work fine (in an unsupported configuration) on Windows 7 well into the future. You should just accept that the environment isn't getting any more care and feeding.Īgain, we're NOT going to add blocks on. NET (in a given environment) when the more foundational operating system is already end-of-life. To my mind, it is incongruent to expect the. NET team won't support them either? It's a much bigger deal that the operating system isn't supported. Your users are not receiving patches for security, crashes, timezone updates, or new hardware. However, you already have to accept that the Windows team is not supporting your users on Windows 7. We're not going to block you from doing that. let's say you have an app and you want to sell it to or support in Windows 7. I want to make a more general observation. We encourage you to migrate to Windows 10 or 11 if you would like to use. Windows Server 2016+ will be supported throughout. NET 7 General Availability) to a newer operating system or plan to purchase Windows Server ESU.
NET 7 on Windows Server 2012/R2 unless you have a migration plan (within a year of. NET 8, assuming you have purchased ESU updates. We will offer support for Windows Server 2012/R2 throughout. Windows Server 2012/R2 ESU will start mid-way through the. At that time, Windows 8.1 will no longer be supported with. Windows 8.1 is supported until January 2023. At that time, Windows 7 will no longer be supported with. Windows 7 will be supported for those organizations until the ESU offering ends, which is January, 2023.
NET 6) for organizations that have purchased Extended Security Updates (ESU). Windows 7 and Windows 8.1 are currently supported with.
0 kommentar(er)
