You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When a project explicitly references the Microsoft.Net.Compilers.Toolset package to pull in a specific version of Roslyn, if that version is newer than the version DocFX ships with (and there are source generators that depend on that version), metadata extraction fails because the source generator assemblies can't be loaded.
To Reproduce
Steps to reproduce the behavior:
Create a project referencing the latest version of Microsoft.Net.Compilers.Toolset:
Describe the bug
When a project explicitly references the
Microsoft.Net.Compilers.Toolset
package to pull in a specific version of Roslyn, if that version is newer than the version DocFX ships with (and there are source generators that depend on that version), metadata extraction fails because the source generator assemblies can't be loaded.To Reproduce
Steps to reproduce the behavior:
Microsoft.Net.Compilers.Toolset
:Expected behavior
No failures when building metadata for a project which builds successfully.
Context (please complete the following information):
This was found from the MonoMod project, when I upgraded Roslyn most recently: https://github.com/MonoMod/MonoMod/actions/runs/10725450864/job/29743290858
I have a workaround here, which forcibly downgrades Roslyn to the version shipped with DocFX when performing the docs build.
If testing on MonoMod, the behavior can be seen with:
dotnet --info
The text was updated successfully, but these errors were encountered: