Website generated output doesn't include all top level namespaces; CHM does include all namespaces

Topics: User Forum
Jul 3, 2014 at 12:32 AM
Good morning/afternoon/other appropriate time of day!

When generating documentation we are seeing the following behaviour: the website and CHM contain slightly different documentation from the same source and generation process in terms of namespaces. The CHM contains all the top level namespaces while the website does not.

Example:

The Website TOC tree in the left pane has the following:
=> A Sandcastle Documented Class Library
=> One top level namespace

The CHM, however, has this:
=> Namespaces
=> Top Level Namespace 1
=> Top Level Namespace 2
=> Top Level Namespace n

The CHM output is basically what we would expect.

I have tinkered with a few of the 'Visibility' settings in 'Project Properties' (re: http://stackoverflow.com/questions/7849679/not-all-namespaces-are-included-into-sandcastle-build-for-documentation) but that didn't seem to help all that much; I could only see one top level namespace.

Thank you very much for all the excellent work. This project is excellent, generating really clean and easy to read documentation. We are very keen to incorporate this into our development environment.

Thanks!

James
Coordinator
Jul 3, 2014 at 2:15 AM
They are all there, you just have to expand the topmost node. The new VS2013 presentation style website output is modelled after the MSDN content so each page contains a TOC fragment rather than the whole TOC. If you've got conceptual content or have enabled the root namespace container option, it will show them on the default page. It's a side effect of how the TOC fragments are generated. For the next release, I'm going to look into having it expand the root node by default if the specific condition is met that causes it to show as it currently does in the collapsed state.

Eric
Jul 3, 2014 at 4:31 AM
Thanks for the quick reply!

It seems to be working now, for whatever reason.