Page 1 of 1

InstallAware Update Script 2.0

Posted: Thu Jul 13, 2006 7:24 am
by MichaelNesmith
Attached is version 2.0 of the InstallAware Update Script.

R&D have worked very hard on incorporating the latest user suggestions and feature requests into this script.

New Features:
* Update checks may now be run directly without prior update configuration. In this case, a "notify me before downloading" option is assumed.
* Once an update has been scheduled, installing a new version of the product will continue the same update on the same schedule, without needing to re-schedule the update.

Bug Fixes:
* Dual configuration dialogs were occasionally shown while running updates under Windows 9X. Fixed.
* If updates were available but all were disqualified by the internal logic of the update script, this caused problems. Fixed.
* Updates were not scheduled under the domain when a user logged on under a domain. Fixed.

Requirements:
* Define a compiler variable called #TITLE# in your setup project, matching the value of $TITLE$. Note: The upcoming release of InstallAware will do this automatically for you.
* When upgrading older update clients, use this code in your setup script:

Code: Select all

 Set Variable NEEDSUPGRADEBACKUP to $NEEDSUPGRADE$
 Set Variable NEEDSUPGRADE to FALSE
 Include Script: updates
 Set Variable NEEDSUPGRADE to $NEEDSUPGRADEBACKUP$

in place of the old code. This lets the new update mechanism (2.0) correctly take ownership of the older (1.0) update mechanism.

Please let us have your feedback so we can refine the update script further, in time for the InstallAware update due very soon.

File Attached:

updates.mia

Posted: Thu Jul 13, 2006 4:58 pm
by Edhy
Hi Michael,

Today I tested this new script and it is working as advertised.

I was able to check for updates without having to setup an schedule.

I tested the /updatesetup and indeed the domain name was added correctly.

Thanks for listening!

Posted: Fri Jul 14, 2006 3:41 am
by Tinus
Sorry, but I run into a new problem.

The shortcuts created in windows\\installer only work if setup is not localised.

To verify this: create a new win 32 project. Set #TITLE# to My Win32 Setup.
Build and install. Shortcuts are created as My Win32 Setup update...

Now export for translation and read back English and German. Build again.
On my German Windows XP I get shortcuts with #TITLE# update now.

Posted: Fri Jul 14, 2006 3:46 am
by Tinus
Please let us have your feedback so we can refine the update script further, in time for the InstallAware update due very soon.

and I like to have an interactive option usefull if called from a shortcut by the user.

This option should:
- not show any ballon messages (no hidden windows)
- give user feedback if no updates are available

Posted: Fri Jul 14, 2006 6:34 am
by MichaelNesmith
Martin

When you are localizing, directly localize the compiler variable - don't leave it as a compiler variable.

The interactive option you describe is interesting, but its not planned for the base feature set at this time.

Feel free to customize the script and post it here for others to share.