You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To be honest, consumers always ask developers to support old systems beyond official EOL. Would you drop Windows 7 just because EOL? Or keep support of it until some significant feature lack?
MSVC has shipped another XP target long after XP EOL.
To be clear, will .NET 5 support Windows 7?
The text was updated successfully, but these errors were encountered:
There might be precedent for dropping Windows 7 based on #423, although I imagine the primary driver for that issue is the difficulty of maintenance as mentioned by @jkotas in a comment. Whether or not a similar case applies to Windows 7, who knows.
We are supporting Windows 7 for the lifetime of .NET Core 3.1. We haven't made a decision on .NET 5 yet, and are not actively discussing it. I suspect we'll until June/July (or later) to make that decision.
To be honest, consumers always ask developers to support old systems beyond official EOL. Would you drop Windows 7 just because EOL? Or keep support of it until some significant feature lack?
MSVC has shipped another XP target long after XP EOL.
To be clear, will .NET 5 support Windows 7?
The text was updated successfully, but these errors were encountered: