Reduce TOC file amount output

[Lucasharskamp]

I have a simple documentation Sandcastle with 10 assembles (.NET 9) on presentation style Default 2022, along with a bunch of custom pages for sake of proper documentation. (with a layout.content file to organize them)

The whole codebase is documented in detail. As you might expect, that's a lot of pages. Now it's not the pages that are the issue here, but the Table of Contents XML files; many of them are generated to be scoped to a specific page you're visiting. Problem is; I'm hosting the documentation on an Azure Static Web App, and it refuses to load them all in, citing there are way too many files I want to upload.

I've tried fiddling around with the settings (binary TOC, etc.), but regardless, it wants to export thousands of files. For the time being, I've disabled TOC generation for the assemblies.

So either I'm missing something which would allow for the TOC to be wrapped into a single file, or this is something that ought to be added.

Preferred solution:

The TOC should be one file for the entire output file for the entire solution; all namespaces and custom files. Once the user enters a specific page, it simply scopes the tree to the page the user is currently visiting, while using the nodes above the page for the breadcrumb. (Using vanilla JS)

[EWSoftware]

The properties in the Help 1 section such as Binary TOC are only used for Help 1 (CHM) files and don't have an effect on website content. I'm not familiar with Azure so I'm not sure why it would have an issue with the TOC files as opposed to the actual topic files themselves as there must be a lot of them too, typically more than the TOC files. Is there some sort of file count limit on the site overall? The TOC generation method used is similar to the one for the much older VS2013 presentation style so it's been around a while.

I don't think having one file is a solution though since then it would have to load that one file for each page which, with a large project, would likely impact performance. That's why its broken up into multiple files. It could probably segregate it by namespace and class instead to reduce the number of files. That would require changes to the TOC plug-in that generates them and the client-side script used to load them.

[EWSoftware]

Replaced by #1156.