-
Notifications
You must be signed in to change notification settings - Fork 370
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
Possible docfx issue with latest SDK #8988
Comments
Looks like this is basically dotnet/docfx#8136 I'm hoping there'll be a new docfx release soon to fix this, but if not we may need to patch things - or pin to an earlier SDK, somehow... |
This shouldn't affect releasing though, so long as we know not to update to a more recent SDK in Kokoro. |
There's a potential workaround, which is to build the docs from the built DLLs instead of the project files. We'd probably want to go via a "dotnet publish" step so that all the DLLs (with the right versions) are in the right directory. However, I think it's probably best to save that approach for a rainy day if we need it. |
I've added a workaround to #8136. We can use that to get local builds working temporarily. Hopefully there'll be a new release soon. |
I'm using SDK 6.0.400 now, and I've just run into a problem running builddocs.sh:
Will try updating to a later docfx version...
The text was updated successfully, but these errors were encountered: