You are here: Features > WebHelp > Merging Output from Flare WebHelp Projects

Merging Output from Flare WebHelp Projects

Use this merging method if you are developing WebHelp or WebHelp Plus output and you want to merge the output files from your "master" project with the WebHelp output files from an external Flare project. This method is useful, for example, if another author is working on the external WebHelp project to which you are linking and you only have access to the output files (not the project files).

Note: There are occasions when projects cannot be merged because the file name is the same in two or more of the linked projects (e.g., multiple DotNet Help projects all named "MyDotNetProject.mchelp," multiple WebHelp projects all named "MyWebProject.mcwebhelp," or multiple HTML Help projects all named "MyHtmlHelp.chm"). The way to solve this dilemma is to make sure each linked project has a different output file name. To do this: (1) open the target, (2) select the Basic tab in the Target Editor, and (3) enter a unique name in the Output File field.

Before your master project can be merged with an external Help system, the output folders and files for the external (or "child") project need to be copied to a folder called "Subsystems" in the same location where the master project is being published. The child's target folder containing these output files also needs to be included at this location.

example

For example, if the master project's output files are being published to C:\MyHelpSystem\Master\Master.mcwebhelp, the output folders and files for the child project should be copied to the folder C:\MyHelpSystem\Master\Subsystems (e.g., C:\MyHelpSystem\Master\Subsystems\AnotherHelpSystem\AnotherHelpSystem.mcwebhelp). In this example, "AnotherHelpSystem" is the target folder that you generated, which holds the output folders and files, and "AnotherHelpSystem.mcwebhelp" is the main output file for the child project that was created. Not only does the main .mcwebhelp output file need to be included in this folder, but also the ancillary output folders and files (e.g., Content, Data, Skin).

You can merge WebHelp outputs using an automatic or manual method.

How to merge output from WebHelp projects (automatic method)
How to merge output from WebHelp projects (manual method)

Note: If you plan to use Mark of the Web (MOTW) and are merging output from multiple Flare WebHelp projects, make sure you enable MOTW in all of the subprojects to be included in the merge. Otherwise, the output will not load smoothly into the browser window for the user. For more information about MOTW, see Adding Mark of the Web and Microsoft's MSDN website.

Note: If you want to create navigation links from content in one project to content in another project, see Inserting Links to External Files.

Note: If you have previously merged Flare projects with WebHelp outputs and then decide to generate WebHelp Plus output from the master project instead, you must make sure that the "child" projects linked to the master contain at least one WebHelp Plus target each. Even if you keep the link from the master project to a WebHelp target in the child, the child project must also have a WebHelp Plus target.

Note: If you merge projects, synonym files will remain separate in each project. For example, if you create synonyms in Project A but not in project B, only the topics from Project A will use the synonyms when users perform searches in the output.

See Also

Downloads (PDF Format):

Flare Quick Guide

Flare Getting Started Guide

Flare What's New Guide

Flare Key Features Guide

Flare Transition From RoboHelp Guide

Flare Transition From FrameMaker Guide

Flare Styles Guide

Flare Printed Output Guide

Flare WebHelp Plus Guide

Flare Shortcuts