-
Notifications
You must be signed in to change notification settings - Fork 867
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
[Feature Request] Support building with preview versions of the .NET SDK #9745
Comments
The above
docfx/src/Docfx.Dotnet/DotnetApiCatalog.cs Lines 129 to 145 in bebcd35
|
It's a shame that roll-forward isn't causing that behaviour to change - that's often a good-enough workaround when I test pre-release versions of .NET where I use global tools that don't yet support them. |
If To force to use .NET9 runtime.
Note It can't use .NET 9 specific features by above settings. |
We can introduce official support for .NET 9 when we retire .NET 7 in May. Supporting a new .NET framework version increases distribution package size. |
This issue can be closed. |
This issue is about previews in general, not support for .NET 9 specifically - if .NET 10 preview 1 has the same problems, then it's still relevant. |
Is your feature request related to a problem? Please describe.
Testing applications out with the .NET 9 Preview 1 SDK, it's not possible to build sites using docfx that have a
net9.0
target framework.This appears to be due to the code below, which requires that the SDK used is the same version as the runtime version docfx uses.
docfx/src/Docfx.Dotnet/CompilationHelper.cs
Lines 135 to 159 in bebcd35
Even if the .NET 8 SDK is installed, in addition to .NET 9's, and
DOTNET_ROLLFORWARD=Major
is set, docfx will still and try to use the .NET 8 SDK to build for .NET 9, which fails.Describe the solution you'd like
docfx allows the use of newer .NET SDKs if installed in the execution environment.
Describe alternatives you've considered
Wait until November until .NET 9 is released and ignore my failing documentation builds.
Additional context
None.
The text was updated successfully, but these errors were encountered: