33.3.4 Deleting MIF files from the project folder
To delete MIF files from the project folder before conversion:
; DeleteExistingMIF = No (default) or Yes (delete *.mif from the
: output directory before the conversion).
When DeleteExistingMIF=Yes, provided both of the following are true, Mif2Go deletes old MIF files from the project folder before conversion:
• [FDK]UseExistingMIF is not set (see §4.2.3 Reusing or discarding MIF files)
• Use existing MIF file if any is not checked on the Export dialog (see §3.7.3 Choosing input source and disposition).
MIFs get deleted on compiling and indexing, also
DeleteExistingMIF takes effect not only when WrapAndShip=Yes, but also when either of the following is true:
See §33.8 Gathering and compiling Help-system files.
As an alternative to DeleteExistingMIF, you could list *.mif as one of the file types for EmptyOutputFiles. Then, MIF files would be deleted before conversion only when the type of conversion (book vs. single file) is consistent with the setting for EmptyOutputDir (see §33.3.1 Specifying when to delete old files from the project folder). However, if you expect to rerun a conversion from the book file after manually deleting only those MIF files you want to replace, do not list *.mif as a file type for EmptyOutputFiles; all your MIF files will be deleted, regardless of what you check on the Export dialog. Use DeleteExistingMIF instead.
> 33 Producing deliverable results > 33.3 Clearing out old files before converting > 33.3.4 Deleting MIF files from the project folder