New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Server 2012 support for .NET Core 3 / 3.1 #3588
Comments
I am also concerned about this issue. |
I know it's near the end of life, but if not supported then |
Windows Server 2012 R2 is the server version of Windows 8.1. Since 8.1 is supported, I think that the Server line just meant "Windows Server 2012 R2+" as a bad update for moving the minimum version from "Windows Server 2008 R2 SP1+" (Win7 server) for the previous version. @centreboard The "Out of support OS versions" section is for versions that were supported, but aren't any more. I believe our statement there is that Win7 Server (2008 R2, even with SP1) is not supported for .NET Core 3.0; probably because the OS itself goes out of support on January 14th (2020). .NET Core 2.1's out-of-support doesn't include Windows XP or Server 2003, since neither of those versions was ever supported. |
@bartonjs That was our reasoning as well. It doesn't make much sense for 2012 not to be supported when 8.1 is still supported. You're probably correct on the change from 2008 R2 SP1. However, since this document seems to be the official OS support statement for .NET Core it'd still be good to get some confirmation. |
I've updated the document to say "2012 R2+". Thanks. |
Jeremy's explanations are correct. Sorry for the confusion! |
If Win2008R2 SP1 is no longer supported, what about the status of Win7 SP1(client). I think they are almost the same(NT6.1), and they share the same RID By the way, 3.1-supported-os.md should also be updated. |
@scalablecory |
Does anyone know that . Net core 3. x supports Windows Server 2008 R2? |
@scalablecory We have the same issue and the documentation update wasn't clear concerning the original question. We have servers running 2012 (not R2) which is supposed for 3.5 more years, has .NET Core 3.0/3.1 officially dropped support for 2012? |
@scalablecory I'd also like to know this. Arguably, the question hasn't even been answered - not clearly at any rate. If Windows 7 SP1 is supported by 3.0 and 3.1, even after all Windows 7 support is gone, shouldn't Server 2012-not-R2 be supported as a going concern? E: And more out of interest than anything else: if it isn't supported on 2012-not-R2, what is it that stops support? Could we monkey-patch it? Can we get it working by just avoiding certain APIs? |
The supported OS page for .NET Core 3.0 (https://github.com/dotnet/core/blob/master/release-notes/3.0/3.0-supported-os.md) shows Server 2012 R2 SP1+ as minimal version for Windows Server. However, as far as we know 2012 R2 doesn't even have a Service Pack 1. Also Windows Server 2012 is still supported for years.
We are currently debating moving from .NET Framework to .NET Core for an on-premise application, and we would expect .NET Core 3 to also support Server 2012, since that still has extended support for several years (possibly longer even than .NET Core 2.1 LTS). So the difference in support between 2012 and 2012 R2 is crucial in deciding whether to go for .NET Core or stay with the .NET Framework.
Can you confirm whether .NET Core 3 (or possible 3.1 LTS) is actually supported on Server 2012?
The text was updated successfully, but these errors were encountered: