Windows Installer Editor Reference
299
Distributing an Installation
z
When the destination computer is started or the end user logs on to Windows,
WiseUpdate Client silently checks the time elapsed since it last ran. If the number of
days elapsed is greater than the check interval value, WiseUpdate Client prompts
the end user to check for updates.
Run from your application
z
On the WiseUpdate page, clear the Add client to Startup group check box.
Entering a value in the Check Interval (days) field is optional.
z
Code your application to open the file WiseUpdt.exe from the application directory,
in either of the following ways:
Run WiseUpdate Client when the application is run.
To use the check interval value from the WiseUpdate page, run WiseUpdate
Client with the /c command-line option. Then WiseUpdate Client silently checks
the time elapsed since it last ran. If the number of days elapsed is greater than
the check interval value, WiseUpdate Client prompts the end user to check for
updates.
Add a menu command in your application to run WiseUpdate Client.
Run silently
You can use this option with either of the options above.
z
On the WiseUpdate page, mark the Only display UI if there is an update to
install check box.
z
On the destination computer, WiseUpdate Client silently checks the time elapsed
since it last ran. If the appropriate amount of time has elapsed, WiseUpdate Client
silently checks for updates. If an update is available, WiseUpdate prompts the end
user to download the update.
See also:
WiseUpdate
WiseUpdate Tips
Can WiseUpdate be used with WebDeploy?
Yes. Make sure that update installations you release are formatted as upgrades (use the
Upgrades page). You cannot use WebDeploy to run patch files (.MSP).
WebDeploy embeds connection information into the .EXE of the .MSI/.EXE pair, so that
the .EXE can run the .MSI from a location on the Web. WiseUpdate provides for regular
checking for updates that are performed by the application on the destination computer.
If you plan to put all compiled files in the same location on the Web, then specify the
same directory on both the WebDeploy and WiseUpdate pages.
Because the .EXE of an .MSI/.EXE pair might contain optional runtimes (examples:
Windows Installer or .NET runtimes), WiseUpdate always tries to open the .EXE, not the
.MSI. Follow these guidelines:
z
The .EXE of the .MSI/.EXE pair must be located somewhere on the Web and must be
accessible to WiseUpdate users. It cannot be distributed through email or other
mechanisms.
