You need to remember this in your deployment scenarios, see below. It has the same name as the CHM file and it is created in the same folder as CHM file. This file is automatically created the first time the Index in generated CHM file is accessed, e.g. To correctly sort and display such more complex index, the CHM runtime needs to create a special. The extended index differs from the basic index in that it contains also the full names of all code members. If you don't plan to open particular topics in your CHM programmatically, we recommend to stay with the basic default index. The disadvantage is that there are no keywords for code member full names and the code above will not work. There are two advantages of this basic index - index is clear and not bloated with too many keywords and mainly, no CHW file is generated (see below). This is fine, since when a user wants to find this method in the Index, he starts to type Method1 and not its full name 1. For example, for 1 method, there is Method1 keyword in the Index. This means that it contains keywords for all code members in a short form. This to work, you need to generate CHM with an "extended" index.īy default, VSdocman generates CHM with just a basic Index which is fully sufficient for use by humans.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |