Rich Lander

> Will code for these OS deleted? For the .NET 6 servicing branch, *absolutely* not. For .NET 7 (`main`), TBD. Once `main` switches to .NET 8, very likely. > MS...

It's very likely that .NET 6 will continue to function the same/correctly on Windows 7 past this date. We're NOT going to do anything intentional to prevent that. There are...

When we remove support for Windows 7, we'll be deleting the support for it from the codebase. That's our policy and it will make us more efficient. We haven't decided...

Good info @Genbox. Data is always good. I want to make a more general observation ... let's say you have an app and you want to sell it to or...

Right. This plan would mean you are stuck on .NET 6 (for Windows 7 scenarios) forever. We did the same thing with .NET Framework 4.0 and Windows XP. .NET Framework...

FYI on Microsoft Office: https://docs.microsoft.com/en-us/deployoffice/endofsupport/windows-7-support

FYI: We're going to start accepting changes in .NET 7 that delete Windows 7 functionality, tests and CI legs. Update: For .NET 7, we'll leave Win 7 codepaths as-is. We'll...

It's very likely that no other platform has as rich of a Windows implementation as .NET.

The team will mostly link to this issue. It should be straightforward to track.

I'm proposing that we move to a single set of ports for both rootful and non-root container images. Here's what that would look like: - For .NET 7 - Rootful:...