[Bug] docfx metadata appears to be broken with 9.0.200

[groogiam]

Describe the bug
After updating to the lates version of the sdk docfx metadata .\docfx.json. The failures seem to be related to blazor framework libraries.

To Reproduce
Steps to reproduce the behavior:

1. Run docfx metadata .\docfx.json in on metadat project that previously worked.

error: D:\source\MyWeb.Ui\Components\Help\HelpLinksComponent.razor.cs(46,32): error CS0115: 'HelpLinksComponent.SetParametersAsync(ParameterView)': no suitable method found to override

Expected behavior
Metadata generation should resolve blazor base classes.

Context (please complete the following information):

• OS: Windows 11
• Docfx version: 2.78.2+3ff9ae7a9700029e0023a7ece18a723d351f1e9b

Additional context
Add any other context about the problem here.

[groogiam]

There is also an warning after all the errors. warning: No .NET API detected for .

My installed SDK's and Runtimes

.NET SDKs installed:
  9.0.200 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 8.0.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 9.0.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 8.0.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 9.0.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 8.0.13 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 9.0.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

[filzrev]

When using .NET SDK version 9.0.103. (It's released at the same time as 9.0.200)
It works successfully.

So I'm suspecting it's caused by .NET SDK 9.0.200 specific problems.

[groogiam]

Is there any way to work around this? I'm kind of stuck between being able to build my documentation or keep Visual Studio up to date as it typically installs the latest SDK releases when it updates. Thanks.

[filzrev]

As a temporary workaround.
It can switch SDK version by using global.json file.

1. Ensure both version of .NET SDKs are installed. (9.0.103 and 9.0.200)
2. Create global.json to source directory with dotnet new globaljson --sdk-version 9.0.103 command
3. Run docfx metadata command
4. Dekete global.json file.

[groogiam]

@filzrev Thanks for the work around. Any idea when the issue might be resolved so the latest SDK can be used? Thanks.

[groogiam]

@yufeih Any update on an ETA for a fix? Thanks.

[filzrev]

Reported issue is caused by .NET SDK (or Roslyn MSBuildWorkspace) problem.
So I thought, it can't be resolved by docfx side.

There are similar issue that relating MSBuildWorkspace and Microsoft.CodeAnalysis.Razor.Compiler on .NET SDK 9.0.200.
But there seems to be no progress at the moment.

• MSBuildWorkspace analyzer results are different in .NET 9.0.200 SDK compared to 9.0.103 and manual compilation roslyn#77255
• Analyzer Tests Fail With SDK 9.0.200 MudBlazor/MudBlazor#10869

[groogiam]

@filzrev It does not seem like these workspace issues have even been triaged at by the Roslyn team. Is there anything that can be done in this code base to work around this? E.g. manually adding the Razor SDK references to the Workspace? Not being able to use the latest SDK in our build pipelines is quickly going to become an issue from a security standpoint. Thanks.

[groogiam]

Reported issue dotnet/sdk#47929 to the dotnet/sdk project.

[filzrev]

@groogiam
Reported issue can be reproduced when using docfx nightly package?

I've tested with project that is created by dotnet new blazor command.
And source generator related error seems to resolved when using docfx nightly version. (That use roslyn package version 4.13.0)
(Note: If .NET 10 preview is installed. It still failed. It need to fix .NET SDK version to 9.0.x by global.json)

If error still continued with docfx nightly version.
It might need minimal reproduceable files.