Inheritdoc behaviour

First, thanks for this great tool!

I wanted to inherit text from another member, and then add it to. I tried:

I tried it as a top level XML:

 /// <inheritdoc cref="Member.ref"/>
  /// <summary>
  /// Blah Blah
  /// 
  /// </summary>

XML:
     <member name="..">
            <inheritdoc cref=".."/>
            <summary>
            Blah Blah
            </summary>

But the output from the tool removes the Blah Blah and you just get the inherited text.

Tried for fun:

  /// <summary>
  /// Blah Blah
  /// <inheritdoc cref="Member.ref"/>
  /// </summary>

and got in the XML:

    </member>
        <member name="M:..">
            <summary>
            Blah Blah
            <inheritdoc cref="Member.ref"/>
            </summary>

Same result.

Is this intentional behaviour?

Many Thanks

[robbyxp1]

Hi, that sorted it, thanks.

I’ve ended up using

    <DefaultDocumentationGeneratedPages>Classes,Delegates,Interfaces</DefaultDocumentationGeneratedPages>
    <DefaultDocumentationFileNameMode>FullName</DefaultDocumentationFileNameMode>
    <DefaultDocumentationRemoveFileExtensionFromLinks>True</DefaultDocumentationRemoveFileExtensionFromLinks>
    <DefaultDocumentationExternLinksFiles>docexternlinks.txt</DefaultDocumentationExternLinksFiles>
    <DefaultDocumentationGeneratedAccessModifiers>Public,Protected</DefaultDocumentationGeneratedAccessModifiers>
    <DefaultDocumentationNestedTypeVisibilities>DeclaringType</DefaultDocumentationNestedTypeVisibilities>

And with a little moving around of the structures into classes (I had some just in the namespace, and they appeared in index.md) there was only a few) both the structures and enums now appear in the class .md file, which is what i wanted.

Thanks you for your help. This is a great tool.

I’ll close it now.

[Doraku]

hum I didn’t plan on having that level of customization for which item has its own page or not but maybe it is possible to add it in the new json configuration format that is coming, I will check how it would work.