This project has moved and is read-only. For the latest updates, please go here.

FQDN dependencies and API filtered items?

Topics: User Forum
Jul 30, 2009 at 6:54 PM

Hey all,

When a type is in a dependency assembly or is filtered out via the API filter list, the unqualified type name shows up in the help. Is there a way to get the type name to be fully qualified in the output in that case?

For example, I have a Method that returns a 3rd party type.

public ThirdPartyCo.CoolType Foo()

If I make ThirdPartyCo.dll a dependency or, via the API Filter, exclude ThirdPartyCo.*, the output in the help for the method foo appears:

public CoolType Foo() 

with the "CoolType" bolded/styled based on the scheme.

Any way to get it be included as the full qualified name of "ThirdPartyCo.CoolType" when it's an excluded type?  


Jul 30, 2009 at 9:14 PM

The display name is most likely controlled via the reference element output by the XSL transformations and the ResolveReferenceLinks2 build component.  You'd have to poke around in the code for the build component to see how it figures out what to display for unresolved links and if there are any attributes that need to be set or added to the reference element in the XSL transformations to get it to display the alternate fully-qualified text.