![]() ![]() Hxreg -n -i wx_documentation -s wx\wx.HxS -x wx\wx.HxI second, we need to register wxWidgets documentation content into this namespace:.Hxreg -n -d "The wxWidgets namespace" -c wx_collection.HxC It has to be unique, therefore I suggest : first, we need to register a "namespace".Now it is time to register the documentation using the hxreg utility. Registering the Help Collection & Help Title To do so, just create the three following files in the previously created directory: Now we need to create a Help Collection from scratch. The wx.HxC is one the files generated in the previous step. The previous step has created some wx.Hx? files but we need more of them before registering the project. And this directory now contains a "Microsoft Help 2.0" project for wxWidgets. This will create a wx directory next to your wx.chm file. So now, I assume that you have both wx.chm and wx.chi files in the same directory. hxreg which will be used to register your help collection and help title to MSDN Library.hxcomp which will be used to compile your newly created "Microsoft Help 2.0" project.hxconv which will be used to convert your CHM files to a "Microsoft Help 2.0" project.(Both of this directories are usualy in C:\Program Files\.) In this last directory, you will find the following executables: Note that when you installed the Integration Kit, it creates not only a "VSHIK 2003" directory but also (and silently) a "Microsoft Help 2.0 SDK" directory. That's where the Integration Kit will help you. ![]() NET Help Integration Kit 2003 Converting the Help 1.x to a Help 2.0 projectĬHM files are "Microsoft Help 1.x" but Visual Studio needs a "Microsoft Help 2.0" project which is basically a bunch of XML files. The overall point is that we need to generate a chi file, because it is needed by the MSDN Library. ![]() If it doesn't, just try using a different *.chm decompiler utility. In some systems it is located in C:\winnt\help. However, note that the location of the "hhcolreg.dat" file may be different. Follow the instructions laid out in the MSDN Integration Utility page. If this occurs, it is still possible to integrate wxWidgets help into MSDN manually. The MSDN Integration Utility will sometimes fail with Visual Studio 6 installations. Hopefully it won't crash the application. So go back to the project options dialog and check the "Compile full-text search information" option and compile the project. ![]() Whenever you newly open the project you have to proceed like this. Afterwards we may activate this option and compile the project safely. Note: To avoid a crashing bug in HTML Help Workshop we always have to compile the project first with the "Compile full-text." option being deactivated. But if we want to have search capabilities in the MSDN Library, we have to make some additional steps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |