question about Merged Projects.

Dear Sir,

merging many sub projects to the master project is Ok when
the compiled sub projects are in the same folder with the compiled
master project. but when distributing the master CHM help file to
customers by its own, the links to the merged sub projects does not
work unless the sub projects chm files are in the same folder with
the master projecis.

please if you have got what I mean please clarify this
situation.

thanks|||
What I do (and it may not be the best way) is to create a
comprehensive index as the first topic in every sub project. This
index leads to every pertinent section in the sub project. This
index is internal and does not reference topics outside the sub
project.

I then merge the sub project into the master project.

Next, I create a master index in the master project. This
links to the indexes in the sub projects. It should reference the
.chm files that have been imported into the master project (i.e.
not the .chm file in the original sub project).

When the master project is compiled it puts all .chm files
into the output SSL directory for the master project.

If you click on the master .chm file in the output directory
you should find you’ve got a composite help file with working links
to the indexes in the sub-projects.

(Watch out for the known RoboHelp bug where – if there are
already .chm files in the output SSL directory for the master
project – they are not overwritten when you recompile).

All the files in the ouptut master SSL directory are then
shipped to the customer.|||


I don’t think you have got my question although you have
answered it in the last sentence of your reply:-

All the files in the ouptut master SSL directory are then
shipped to the customer.

I thought merging projects enable us to send customers only
the master CHM file.

any ways I have another question regarding merged projects
too, When I make a hyperlink to an external topic, I cannot open in
a new window or in a pop up window.

Related posts:

1. Merged projects
2. Going from single project to merged projects
3. Including parent and sibling TOC in all merged project sub-projects
4. Linking within merged projects
5. Linking within merged projects

Related posts brought to you by Yet Another Related Posts Plugin.