-
Notifications
You must be signed in to change notification settings - Fork 653
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
Minimum .NET version now 8.0 #6980
Comments
To clarify here, we only upgraded the runtime that the language server uses to .net8. We can still load projects targeting .net6, .net7, .net8, etc. regardless of what runtime we use to run the language server. Additionally, the runtime used by the language server should be relatively transparent to you - if .net8 is not found on the path we acquire it via the runtime installer extension. @rjra100 I notice from your logs that we determined .net8 was not installed - but it looks like it isn't being acquired by the runtime extension properly. Do you have any custom configurations setting the |
Fair - but at least one reason to be targetting .NET 6 or 7 is that that's the latest version that the OS in question supports. We've still got a lot of stuff on RHEL7 (don't ask), and I don't think .NETs more recent than 6 are supported on that. Fortunately we're almost in a position to switch our main development stream to RHEL8, so it's not as bad as it could be for us - but we're probably not the only ones.
No, though I do have a DOTNET_ROOT environment variable. However, I think the failure to download via the runtime extension is probably a local environment glitch - I have a local instance of NodeProxy which is supposed to direct things via the appropriate proxies for our excessively-complicated network setup, and it periodically dies. After I restarted that this morning, it does successfully download a runtime via the runtime extension (at least so long as I'm in the RHEL8 environment). |
@v-Judy looks like a slightly different issue on the Razor side - I filed dotnet/razor#10132 to track that on their side.
I think it was .net8 that dropped rhel7 (ref). In this case, since .net7 is EoL in 2 months anyway and rhel7 1 month later (plus .net8 is LTS), we feel its reasonable to take the upgrade. If rhel7 support is required, it's always possible to downgrade the extension version. |
Closing this as by design (Razor issue tracked separately). |
Type: Bug
The minimum .NET version for the C# extension now appears to be .NET 8.0 (as of C# extension v2.22.3)
Per https://dotnet.microsoft.com/en-us/platform/support/policy, .NET 7.0 is supported until May '24 and .NET 6.0 should be supported until November '24. Isn't dropping support for these in the extension a little premature?
Guess I'll go upgrade to .NET 8.0 (but some people are still stuck on RHEL (or CentOS) 7 and .NET 6.0)...
Output from C# pane:
Extension version: 2.22.3
VS Code version: Code 1.87.2 (863d2581ecda6849923a2118d93a088b0745d9d6, 2024-03-08T15:20:17.278Z)
OS version: Windows_NT x64 10.0.19045
The text was updated successfully, but these errors were encountered: