Plugging into VS help is not happening automatically
I'm using an *.msi file to install a help (MS Help 2.0) project that is
supposed to plug-in as a child to MS.VSCC.2003. It installs the files and
there are no errors, but it does not plug-in to the VS help. If I open the
Collection Manager
(ms-help://MS.VSCC.2003/VSCCCommon/cm/CollectionManager.htm), it is listed
as it should be, but the checkbox is not enabled. If I check it and press
the Update VSCC button, my collection does get correctly plugged in (after a
wait of about 2 minutes when I next launch VS) and it works fine.
I *think* that the fact that I'm able to see my collection in the Collection
Manager, and the fact that the Collection Manager can plug it in perfectly,
means that all my files are correct. So does anyone have any ideas on why
the plugging in does not occur automatically at installaion time?
P.S. I've tried both hierarchical and flat plugin styles. Same symptoms with each.
Thank you,
[978 byte] By [
Rickee] at [2008-2-2]
Hello,
So your content is on the box, but isn't getting plugged into MS.VSCC.2003.
Just to make sure, you're trying to plug content into Visual Studio 2003, right? What method are you using to create your Msi that installs documentation? Are you utilizing the Help Integration Wizard?
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/integration_wizard.asp
Or are you following instructions in VSIP Help (VSHIK) to edit merge modules in your installer in order to achieve the plugin of content?
Thanks,
Jeremy Jones
I have found the cause (and fix) of this. It results from some errors in MS's documentation.
In at least two places, the documentation discusses changes you make to the file MSHelp2_RegTables_RTL__.msn with the Orca editor. Here are the problems:
1. For the table HelpNamespace the instructions say that you should enter <company prefix>.<collection>.<language ID> in both the NamespaceKey and the NamespaceName columns. Actually, in the first of these you should enter <company prefix>_<collection>_<language ID>. Note how underscores replace the periods. (Use periods, as instructed, for the NamespaceName column.)
2. In the table HelpFileToNamespace, use underscores, not periods, in the HelpNamespace_ column.
3. In the table HelpPlugin, use underscores, not periods, in the HelpNamespace_ column and HelpNamespace_Parent columns. Also, the File_HxA column should be blank, if there is no HxA file. Do not enter "_DEFAULT" as the instructions say in at least one place.
