DocumentInheritedMembers = true, DocumentInheritedFrameworkMembers = false

Topics: User Forum
Sep 3, 2010 at 6:09 PM

DocumentInheritedMembers = true, DocumentInheritedFrameworkMembers = false

I thought with that combination that I would get inherited members from my own classes, but not those from the framework. However, what happens is all the classes have only the main class page, no properties page, no methods page, no all-members page, no sub-nodes at all in the TOC. Just a flat list of classes.

Is this a bug? Thanks..

David Rizzi

Sep 3, 2010 at 10:59 PM

Followup: I found a work-around. I set both to true and then used the API filter to filter out the portions coming from the framework. Not as clean as I had hoped, but it works.

David Rizzi

 

 

Coordinator
Sep 4, 2010 at 9:24 PM

When DocumentInheritedMembers is set to False,  SHFB removes all inherited members with an ID starting with "System." or "Microsoft." and it will leave all other inherited members in place.  You shouldn't have any issues unless your code is in a namespace starting with one of those prefixes.  I've tried it out in my test project and didn't see the issue you encountered.  If you can create a test project that demonstrates the problem, I can look into it.

Eric