In Help+Manual you can enter these settings in Configuration > Publishing Options > Visual Studio Help > Namespace & Options.

Visual Studio Help 2008 (HXS)

The Help 2.0 compiler requires a "namespace" and a "unique identifier" (also referred to as a "Unique Title ID" in the documentation). Both must be entered otherwise the compiler will quit with an error message. (The namespace is used to call the help viewer, the unique identifier is like a Topic ID for the entire help file.)

Visual Studio Help 2010 (MSHC)

The Help 3.0 format only has three required settings: The vendor name (the company that owns the book and packages), the product name (the name of your product) and the book name (the name of your book). The fourth required setting is the locale, but that is inserted automatically by Help+Manual on the basis of the language setting in your project.

Note that in MS Help 3.0 a "package" is a single MSHC help file. A "book" is a group of packages that you install together. A package can belong to more than one book.

Unlike HTML Help CHM files you cannot just copy a Visual Studio Help HSX or MSHC file to your disk and then click on it to start it. It must be installed and registered first.

Visual Studio Help 2008 (HXS)

When you publish HXS files with Help+Manual they are installed and registered automatically on your development machine so that you can view them there. However, when you distribute your files you must configure the MS Installer to do this. See the documentation of the installer and your Microsoft Visual Studio package for details.

Visual Studio Help 2010 (MSHC)

Visual Studio Help 2010 MSHC files must be installed with the Visual Studio Help Manager. Please see the VS documentation for details.

If you reference any additional files in your HTML topic templates you must add them to the Baggage Section in the Project Files section of the Project Explorer. MS Help 2 does not have anything like an .HHP file with which you can tell the compiler to include additional files. (Yet another surprising limitation compared to Microsoft's other earlier help formats.)

If you add files to the Baggage Section they will be included in your published output automatically.

Note this option only applies to Visual Studio Help 2008/MS Help 2.0.

Help+Manual supports two different compile options for Visual Studio Help. Normally you will compile a finished HXS file, which will then be automatically registered on your local development computer and opened. If this does not work properly there is also a debugging option called Do not compile, open with VStudio in the Publish dialog.

•If you select the Do not compile option Help+Manual generates a Visual Studio Help Project file with the extension .HWProj in the temporary output directory. This is a small XML file that acts as a wrapper for Visual Studio.

•When you select this option the temporary output directory (in your project directory) is not deleted after you compile the project. After publishing you can then use the .HWProj file to open and compile the project file directly in VS.Net, using the debugging options available there.

The following two calls are just brief examples. For full details please refer to the documentation of VS.NET and the VSHIK!

Manual registration of an .HXS file:

"C:\Program Files\Microsoft Help 2.0 SDK\hxreg" -n Namespace -i UniqueID -c MyHelpfile.HXS

Call to view an .HXS file:

"C:\Program Files\Common Files\Microsoft Shared\Help\dexplore.exe" /helpcol ms-help://ECSoftware

As you can see there is no file name in the call. In the above example ECSoftware is the Namespace. The viewer will only find the file if it has been registered correctly.