Software Deployment

Here are the command lines for WFWI.EXE (straight from the Help docs):

/c Compile only and exit. This must be the first option in the command line statement.

/c="release name" Compile only the specified release from an installation containing multiple releases.

/p name=value Set property values. The property name and value must immediately follow the /p. You can use as many property name and value switches as you like in a command line. Do not enter any spaces in the name=value construction, unless they are enclosed in double quotes.

/o path Specifies the compiled output file. You cannot specify a relative path; specify an absolute path. The path must immediately follow the /o.

/F Has the same effect as clearing the Don't update or recompress files when saving checkbox on the Product Details Page.

/s Causes the compile to be silent. If you don't include this, error or informational dialogs might appear that require user intervention.

/l log file name The /l followed by a log file name makes an additional compile log file, in addition to compile.log, which is created automatically.


As you can see, there is no "/n" switch. I would look into using the Macros feature so that your script (to make a backup of the .WSI) would run on the "Open" event. The only problem here is that you need to change your .wsi template so that it has the macro script in it by default. (Otherwise you need to add the macro script into every .wsi)

Sound about right?

Thank's for the response. "About right", but not correct. I have read the help documents, and KB article 791 at Wise.

/C /S "[ProjectDir]\[FileName].wsi" will compile my the package silently creating a WSI and MSI.

I just want a backup copy of the WSI file before the packagers start the edit process. Don't want to confuse new packagers with a prompt to overwrite exsisting package when they are done editing.

Kent