Microsoft Visual Studio uses a proprietary Help system known as Microsoft Help 2.x; codenamed "Havana". The Microsoft Visual Studio SDK ships a number of components for extending Visual Studio, including its help system. [For more information regarding Visual Studio Extensibility and the Microsoft Help 2.x help system please install the Visual Studio SDK.]
It will also allow you to register new Namespaces, HxS files, filters, and plugins as well as to unregister or delete the same. You can also register files to use an .HxQ/.HxR with this tool. The main uses for the original Namespace tool are for obtaining information about a registered Help collection as well as for hacking existing collections or registering new ones for experimentation purposes. There have also been a number of other little one off internal Microsoft help tools that enabled you to inspect a few other features of the help system. Microsoft Namespace# 2.0 endeavors to wrap all of the features of the original Namespace and other internal Microsoft help related tools into one tool, and also adds features similar to the DExplore help viewer that currently ships with Visual Studio. But it also goes much further, allowing you to explore the internals of individual help files, view scripts and .css files that are used, view collection definition files and much more. It is sort of intended to be a one stop shop for exploring nearly every detail related to Help 2.x help systems. Two primary areas to look at are the Namespace and Help View tabs in the UI - these toggle between a diagnostic view of the help system to a more help viewer type mode. The Help view mode is based on the collection/namespace you currently have selected in the Namespace mode. There are many features buried in this tool. * TIP * - right click on the tree nodes in the Namespace view to see a number of tasks that you can perform. Requirements Microsoft Namespace# 2.0 assumes that you have some product installed that has already installed the Microsoft Help 2.x help system (i.e. Visual Studio, etc). For a few fringe features (HxQ/HxR generation) it would also require the Visual Studio SDK to be installed, though this is not required for its most common uses. |