Replies: 1 comment
-
Remove the leading slash on the path when at the root level. It's likely a matter of evaluation context though I'd have to test it to be sure. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am using the Default2022 style.
I notice that top-level inheritance of constructs in XML code documentation works with intellisense within Visual Studio but doesn't seem to work in terms of getting processed the same way when generating documentation. Consider the following:
The compiled .xml documentation file looks like (with <inheritdoc> tags):
The temporary SHFB file InheritedDocs.xml file looks like:
The class does not inherit the method's remarks.
It is interesting to note that if the top-level tag
gets nested and surrounded by a standard top-level tag
that the remarks get inherited as expected.
So, the question is how to get the new Default2022 style to process standard (or custom) top-level <inheritdoc> tags? The differences above with inheriting remarks is probably cosmetic in most cases as it would be essentially equal to do just the 2nd nesting option but there are ramifications when trying to apply the 1st option to tags like <param> which are top-level tags and not nested.
Beta Was this translation helpful? Give feedback.
All reactions