Omni Systems, Inc.

  

Mif2Go User's Guide, Version 33u53

  

Valid HTML 4.01!

 

Made with Mif2Go

33 Producing deliverable results > 33.4 Assembling files for distribution > 33.4.5 Emptying the assembly folder before copying


33.4.5 Emptying the assembly folder before copying

To clear out the assembly folder before Mif2Go copies files:

[Automation]

WrapAndShip=Yes

; EmptyWrapPath = Yes (default, remove all files before copying)

; or No (leave old files in place in WrapPath directory)

EmptyWrapPath=Yes

When EmptyWrapPath=Yes, provided WrapPath does not point to the project folder, Mif2Go deletes the entire contents of the WrapPath folder before copying files. However, if either of the following is true, Mif2Go does not delete anything, regardless of the value of EmptyWrapPath:

neither the configuration file nor any referenced template has a setting for WrapPath

WrapPath points to the project folder.

For HTML output types, if WrapPath points to the same folder as [Graphics]GraphPath, Mif2Go does not delete files unless both EmptyWrapPath and EmptyGraphPath are set to Yes; see §33.5 Placing graphics files for distribution.

When EmptyWrapPath=No, Mif2Go leaves the prior contents of the WrapPath folder in place. Orphaned and obsolete files from previous conversion runs could accumulate and find their way into current deliverables. For this reason, it is better to designate a folder for WrapPath that is different from the project folder, and set EmptyWrapPath=Yes; that way nothing important is lost, and nothing unwanted is delivered. 

Note:  

EmptyWrapPath takes effect not only when WrapAndShip=Yes, but also when either of the following is true:

CompileHelp=Yes

FTSCommand=path/to/indexer

See §33.8 Gathering and compiling Help-system files.



33 Producing deliverable results > 33.4 Assembling files for distribution > 33.4.5 Emptying the assembly folder before copying