feat: Add .NET 9 support (and drop .NET 6 support)#10239
Conversation
|
For a tool, is there any real need to even drop support for the framework before the support ends? |
|
I'm expecting this PR is merged and released newer docfx version after .NET 9 RTM release. The reason I've dropped
|
9378daa to
2aac9d1
Compare
If I understand it well, this normally should not be an issue. Reference the version that supports the .NET 6 for the .NET 6 build.
Just updated my version to If data are later downloaded, I will assume these are not Framework dependent. Again, I might be missing something. |
2aac9d1 to
df2940d
Compare
|
I agree with dropping unsupported .NET versions to reduce unneeded maintainance effort. This will to be merged and released after November 12, 2024. |
Please ignore the above comments. For docfx users. keeping .NET 6 support requires about In any case, I would like to drop .NET 6 support to lower maintenance costs with following reasons
For users who continue to using .NET 6. It need to use version that supports .NET 6( |
|
What's the ETA on a new version including this change being published to NuGet.org? |
|
@martincostello A new release has been published to NuGet.org today with .NET 9 support. |
This PR including following changes.
go-live)November 12, 2024)Note:
The SDK for Self-Contained exe zips will remain .NET 8.
Because it's .NET 8 is
LTSrelease and longer support lifetime.