[Bug] Failure with inheritdoc under certiain circumstances

[Lesnik4u]

Actual behavior
docfx fails to inherit documentation when <inheritdoc> is used under certain circumstances:

• inheriting from .net type (e.g. object.ToString(), object.Equals(), etc) and
• project TargetFramework is "netstandard2.0"

Please note that doc inheritance works well:

• for other TargetFramework, e.g. "net6.0"
• for types created within the project, e.g.
• with Visual Studio hint

Expected behavior
Documentation should be inherited like it happens for other target frameworks or for other types.

To Reproduce
See minimal sample project here:
https://github.com/Lesnik4u/DocFxInheritdocIssueTest
particularly, see the override MyLibBaseClass.ToString().

namespace MyClassLibrary
{
    /// <summary> Description in the BASE class. (TargetFramework = netstandard2.0) </summary>
    public class MyLibBaseClass
    {
        /// <summary> Description in the BASE class. </summary>
        public virtual void MyMethod() { }

        // inheritdoc FAILURE!
        /// <inheritdoc/>
        public override string ToString() => "";
    }


    /// <inheritdoc/>
    public class MyLibChildClass : MyLibBaseClass
    {
        /// <inheritdoc/>
        public override void MyMethod() { }
    }
}

Context:

• OS: Windows 10 pro
• Docfx version: v2.73.1
• .NET Core SDK: v6.0.300

[yufeih]

The behavior matches IntelliSense in vscode, so it might be a bug with MSBuildWorkspace or roslyn. Not sure if out of proc MSBuild would resolve this:

[filzrev]

it might be a bug with MSBuildWorkspace or roslyn. Not sure if dotnet/roslyn#61454 (comment) would resolve this:

As far as I've tested with latest roslyn version.
It's not resolved by out of proc MSBuild.

I thought it's relating following problem that described at this comment

Ref assemblies don't have documentation at build time,

[yufeih]

The behavior matches IntelliSense in vscode, so it might be a bug with MSBuildWorkspace or roslyn. Not sure if out of proc MSBuild would resolve this:

[filzrev]

it might be a bug with MSBuildWorkspace or roslyn. Not sure if dotnet/roslyn#61454 (comment) would resolve this:

As far as I've tested with latest roslyn version.
It's not resolved by out of proc MSBuild.

I thought it's relating following problem that described at this comment

Ref assemblies don't have documentation at build time,