### 8.2.6 Deciding whether to regenerate the WinHelp project file

When you use Mif2Go to generate WinHelp from within FrameMaker, Mif2Go writes an .hpj project file during set-up, and rewrites it later only under certain conditions.

To specify whether Mif2Go should generate the .hpj project file anew each time you run the conversion:

[HelpOptions]

; WriteHelpProjectFile = Yes (write each time) or No; if no setting,

; write only if the file does not already exist.

WriteHelpProjectFile = Yes

The values you can specify for WriteHelpProjectFile have the following effects:

Yes | If the .hpj file is present, Mif2Go overwrites it.
No | Mif2Go does not overwrite the .hpj file.
(none) | If the configuration file contains no WriteHelpProjectFile setting at all, Mif2Go writes an .hpj file, but only if the .hpj file is not already present.

Mif2Go closes the .hpj file after writing it; however, if you had the .hpj file open in Help Workshop when Mif2Go rewrote it, you could get an access violation. (Notepad would just rewrite the old file over the rewritten one.)

If you set WriteHelpProjectFile=Yes and then later decide to modify the .hpj file, be sure to set WriteHelpProjectFile=No; otherwise your edits will be wiped out the next time you convert.

If you use Help Workshop to make changes that are not reflected in the configuration file, and they are changes you want to keep, you can prevent Mif2Go from overwriting them by setting WriteHelpProjectFile=No.

| 8.2.5 Understanding initial set-up requirements |  | 8.2.7 Accommodating platform differences |