TCynthesisAppUpdate

The TCynthesisAppUpdate component provides an application with the capability of automatically checking the web for updates to your application, and automatically downloading and installing the update if one is found. This page provides more detail on the component.

Please: If you have any problems with the component whatsoever, from installation to potential bugs, please get in touch with me via e-mail . That's the only way I can improve the component!

Download TCynthesisAppUpdate for Delphi 5 now! (540K ZIP File)
Download TCynthesisAppUpdate for Delphi 4 now! (540K ZIP File)

Download ZipMaster Now! (500K ZIP File; used by the TCynthesisAppUpdate component)
Note: I have made some small changes to the ZipMstr.pas file - you should use the one that comes with the AppUpdate component, or make the equivalent changes in the ZipMstr.pas source in the ZIP file above.

Download the Internet Component Suite Now! (970K ZIP File; used by the TCynthesisAppUpdate component)

Date:	8/10/2000
Version:	3.0.0.0
Author:	James Waletzky
E-Mail:	[email protected]

Contents

Requirements

• Delphi 5.x (ApUp??D5.zip) or Delphi 4.x (ApUp??D4.zip) with Update Pack #2 or later
• The Internet Component Suite (ICS) by Francois Piette must be installed. You can download the source for this package from from http://www.rtfm.be/fpiette/indexuk.htm, the Delphi Super Page, or from the Cynthesis web site.

Installing TCynthesisAppUpdate

1. Uninstall any previous versions of the AppUpdate or ZipMaster component. Either remove the packages in their entirety that contain these components (unchecking the package names from the "Install Packages" dialog (Component | Install Packages), or remove the individual components from the packages of note.
   
   Remove all instances of any DCU, BPL, and DCP files that were distributed with previous versions of AppUpdate.
   
2. Install the ICS components that you downloaded earlier (see Requirements  section above) in the manner described in the README.TXT file distributed with that package. Be sure to install the version applicable to your version of Delphi (ICSDEL40 for Delphi 4, ICSDEL50 for Delphi 5).
   
3. Unzip the ApUp*.zip file (make sure that your zip program preserves the paths in the ZIP file as the project settings are configured to use the paths embedded within the ZIP file).
   
4. There will be a subdirectory under the directory that you unzipped to called either Delphi4 or Delphi5, depending on what version of the component you downloaded. Locate the BPL and DCP files in that directory for the TCynthesisAppUpdateD? package and the ZipMasterD? package (where ? is 4 or 5 depending on your version of Delphi).
   
   Move the BPL and DCP files to a location on your hard drive that is in the path (the place where the rest of your Delphi packages are installed should work). You will experience problems starting Delphi if the BPL packages are not placed in your path.
   
5. In Delphi 5 (Delphi 4 is similar), click the "Component" menu followed by "Install Packages". In the dialog that appears, add the ZipMasterD?.BPL file.
   
   If things worked correctly, you will end up with a "Samples" tab on your component palette with the ZipMaster component on it. Note that if you have the ZipMaster component installed in another package, you will need to remove it from that package prior to installing the AppUpdate component. The version included with the AppUpdate component has some special modifications for localization of ZIP file messages.
   
6. Using the same procedure, add the TCynthesisAppUpdateD?.BPL file.
   
   If things worked correctly, you will end up with a "Cynthesis" tab on your component palette with the AppUpdate component on it.
   
7. Try building and running the sample application, AppUpdateTest.dpr. For more information on building the sample application and your own applications, please see the Usage section.

History

Known Problems (as of Version 2.2.0.0)

• Sample Application: The browse button in the sample application is not working as expected. I have yet to look into this. Again, if you have any ideas, please e-mail me. For now, just type in the path to the DCU file.
  
• Sample Application: If you get a message that there is a new component update available, you cannot change tabs in the test application until you've downloaded the update. If you don't want the update, simply quit the test app and reload to once again experiement with the sample.

File Contents

• Documentation:
  • Readme.html: this file (also available on-line)
• Packages:
  • For ApUp??D4.ZIP:
    • TCynthesisAppUpdateD4.bpl: Delphi 4 package
    • TCynthesisAppUpdateD4.dcp: Delphi 4 package output
    • ZipMasterD4.bpl: Delphi 4 package
    • ZipMasterD4.dcp: Delphi 4 package output
  • For ApUp??D5.ZIP:
    • TCynthesisAppUpdateD5.bpl: Delphi 5 package
    • TCynthesisAppUpdateD5.dcp: Delphi 5 package output
    • ZipMasterD5.bpl: Delphi 5 package
    • ZipMasterD5.dcp: Delphi 5 package output
• Demos:
  • AppUpdateTest.dpr: sample application project file.
  • AppUpdateTest.dof: project settings for sample application.
  • AppUpdateTest.cfg: config file for sample application project.
  • AppUpdateTest.res: resource file for sample application.
  • AppUpdateTest.ico - icon file for the test application.
  • AppUpdateTst.dfm: main form file for the test application.
  • AppUpdateTst.pas: source code for the main form file.
  • frmUpdateInfo.dfm: form to display details about an available update
  • frmUpdateInfo.pas: source code for update info form
  • SampleAppUpdate.ini - Sample update information file.
• Compiled files and Source files:
  • AppUpdateMessages.res: resource file containing message strings (for component and helper).
  • CynthesisAppUpdate*.dcu (Delphi 4 or Delphi 5): The DCU files should you wish to statically link the component to your application.
  • CynthesisAppUpdateTypes.pas: Various types used by the AppUpdate component
  • Update.exe: companion helper application that takes care of installing the update.
  • UnzDLL.DLL - Helper DLL used for unzipping files from the update archive.
• Language Support:
  • German\AppUpdateDE.DLL - German resource DLL.
  • Italian\AppUpdateIT.DLL - Italian resource DLL.
• ZipMaster Component:
  • DCU files (located in the Delphi subdirectory)
  • Source files for the ZipMaster component (get the full component here)

What is the TCynthesisAppUpdate Component?

The TCynthesisAppUpdate component provides the functionality to an application of automatically checking for new versions when on-line (via a HTTP web connection, FTP connection, or network connection), and downloading and installing application updates. The component can handle the entire update process using its own user interface, or you can capture a few simple events and handle the update process manually. Dropping the component on your application's main form, setting some properties, creating a simple INI file, and placing both the INI file and the zipped update on a web server, FTP server, or network drive are all that's required for your application to update itself!

Other features include:

• Delphi 4 and Delphi 5 support (with included packages)
• get updates via HTTP, FTP, or network drive (LAN/WAN)
• provide detailed information about available updates to the user prior to download
• different modes of update, including the options of having the component provide the update UI, providing your own update UI, or having the entire update process run without any UI.
• version information in executable compared to version information on remote server
• support for network configurations with proxy servers on particular proxy ports
• support for username and password information when retrieving updates
• distribute your binary files in a ZIP file and have the component handle the update; or
• distribute your update as an executable (EXE) that is run once the download process has completed.
• specify which versions of your application that the udpate is compatible with (you may not want to install a v5.01 update over a v1.0 binary) using smart version comparison.
• easy localization to any language (English is the default; German and Italian resource DLLs included).
• the Update helper application will close the application to be updated before applying the update
• the Update helper application will list the files that have been updated (when distributing your update using the ZIP method).
• the Update helper application will offer to run the updated application with its original command-line parameters.
• events are fired to your application for all important actions.

If you have any great ideas for features in this component (or additional components), please be sure and let me know !

Limitations of Use

The TCynthesisAppUpdate component (and its various pieces) is free for non-commercial use . All I ask is that you send me an e-mail telling me that you are using the component. For use in a commercial application , please contact me (James Waletzky) via e-mail at [email protected] for licensing details. Cynthesis software has the right to charge a fee for use of this component in a commercial application. Please contact me for commercial licensing and I will forward the license agreement to you via e-mail.

Note: A commercial application is an application that you have developed from which revenue is derived, such as sales, license fees, development contract fees, advertising, etc.). A non-commercial application (or freeware) is an application you have developed from which no revenue is derived, and is provided to the public domain without usage restrictions.

The source code for this component is available by donation from Cynthesis Software for a suggested cost of $10 (US Funds). Higher denominations are encouraged, however, to fund future development. The source code may be modified for your use but may not be redistributed. You may include the source code in any non-commercial applications that you develop without royalty. To purchase the source code please remit a cheque or money order payable to Cynthesis Software Inc. to the following address:

Cynthesis Software Inc.
408 - 260 Newport Drive
Port Moody, BC
Canada
V3H 5C6

If you decide to make use of this component, I would like to hear from you as to your comments about the component, or suggestions for improvement.

IMPORTANT: Telephone support will not be provided for this component. All correspondence must occur via e-mail.

Usage

General

1. Install the TCynthesisAppUpdate package as per the instructions above.
2. Drop the component on your application's main form.
3. Add CynthesisAppUpdateVersionInfo and CynthesisAppUpdateTypes to your uses list.
4. Decide what online mode (HTTP, FTP or LANWAN) you want the component to use.
5. Determine whether you want the component to handle the entire update or you want to do it manually via events (set the UpdateMode property).
6. Fill in the current version of the product, or ensure that the version information in the project settings is up-to-date.
7. Fill in the URL (for HTTP), FTP host name, or network location that will point to the update information INI file, and any other properties you desire..
8. [Optional] Fill in the ResourceDLL property to point to the DLL that contains your string resources (path information not required if the resource DLL is in the same directory as your application executable). If you are distributing your application and want to use English messages, this field may be left blank.
9. Distribute your application (don't forget to include UPDATE.EXE in your distribution package in the -same directory- as your application executable). You should also install UnzDLL.DLL in the Windows directory.
10. When it comes time for an update to your application, create an INI file as described below.
11. Prepare the update information INI file.
12. Upload the INI file and the update file to a web server as indiciated by the UpdateInfoURL property.

Early Binding vs. Late Binding

The component, as distributed without source code, works best if you configure your applications to use the TCynthesisAppUpdateD?.BPL, ZipMasterD?.BPL and ICSDEL?0.BPL files as run-time packages (late binding). You can set this property in your project settings on the Packages tab by selecting the "Build with runtime packages" checkbox and ensuring that the edit box contains entries for TCynthesisAppUpdateD?, ZipMasterD?, and ICSDEL?0.

To statically link in the AppUpdate, ZipMaster and ICS components into your application (early binding), you should ensure that "Build with runtime packages" is left unchecked (or the AppUpdate, ZipMaster and ICS packages are removed from the edit box) and add the paths to your AppUpdate, ZipMaster and ICS DCU files to the "Search Path" entry on the "Directories/Conditionals" tab in the project options. This will cause Delphi to link in the DCU files instead of use the packages at run-time. This works in my test configuration, but the odd person has had trouble getting their application to build. If you can't seem to work through the problems, I recommend purchasing the source code, as that will alleviate all problems.

About the Sample Application

The sample application illustrates how to use the TCynthesisAppUpdate component in a couple of different ways. It consists of two tabs - one that allows you to update the sample application itself using one of the specified protocols, and another tab to update this component package. The first tab takes a modal dialog approach and informs the user when the update is available, provides full information about the update, asks the user to download, etc. via dialog boxes. The second tab updates the component package via a changing button state (run it to see what I mean). When an update is available you will be presented with an edit box where you fill in the path where your component files reside. The update will unzip the new version over top. For full details on how this works, check out the source. I have tried to comment it fairly thoroughly.

Note: The sample application has not been translated to languages other than English. Therefore, if you set the ResourceDLL property on any of the AppUpdate components on the sample form, some messages will remain in English.

Note: Make sure that the path to the ICS source code (<path>\ICS\Delphi\VC32) is listed in the search path of the sample application project options.

Update Info INI File Format

The Update Info INI File describes the most recent application update that is sitting on the web server. The TCynthesisAppUpdate component first downloads this INI file to determine whether an update is necessary before downloading the update itself. You will need to create an INI file and upload it to the location specified in the UpdateInfoURL property of the component every time an update is available.

The format of the INI file is as follows (anything that appears in angle brackets <> should be replaced):

[UpdateInfo]

Name	Value
Name	[string] any string that describes the application (usually just the name of the application).
Version	[string] version number of the update; usually in the following format: w.x.y.z
InstallAction	[string] see the InstallAction property on the component for details. The actual strings that should be present in the INI file that map to the InstallAction enumerations are (leave out the quotes when inserting these strings into the INI file): iaNone -> "None" iaUseUpdate -> "UseUpdate" iaRunExecutable -> "RunExecutable"
UpdateURL	[string] Location of the zip or executable file that represents the update. When the OnlineMode property of the component is set to olHTTP, this must be a URL (example: http://www.npsnet.com/waletzky/samples/sampleappupdate.zip) URL to the zip or executable file that represents the update. When OnlineMode is olFTP the UpdateURL must be in a special format of host/path/filename or be a complete FTP URL. (example: ftp.npsnet.com/waletzky/samples/appupdate.zip or ftp://ftp.npsnet.com/waletzky/samples/appupdate.zip ) When OnlineMode is olLANWAN this must be in one of two formats: standard Windows path format: d:\path\filename OR \\machine\sharename\path\filename (UNC Format) (examples: c:\waletzky\samples\appupdate.zip or \\waletzky\sharedir\samples\appupdate.zip )  Note: all lowercase is recommended for this value as well as the actual name of the file and directories on the server when OnlineMode is olFTP to avoid case sensitivity issues.
ReadmeURL	[string; optional] URL to a README file that describes the update. The README file is a good place to place detailed and formatted release notes about the update so that the user may make an informed decision as to whether the update should be downloaded and installed.
Details	[string; optional] any text used to describe the update; could be an abbreviated list of changes. This is not used by the component other than to be made available to your event handlers via the property INIDetails.
SmartCompare	[boolean]Indicates the type of comparison that is performed when comparing version information. When SmartCompare is False (default), the version strings are compared alphanumerically. With SmartCompare True then at each segment of the version number (dot-delimited segments), comparison is done numerically if and only if that segment of both version numbers is comprised entirely of numeric digits. Also when SmartCompare is True you can use '*' as a segment wildcard in the INI variable CompatibleVersions (see below). Wildcards are NOT allowed in the INI variable "Version" or in the component property "CurrentVersion". (Any asterisk present in those two values is treated as a literal character.) SmartCompare is especially useful when the component's CurrentVersion property is left blank to cause CurrentVersion to be extracted from the exe's embedded version number. Examples: With SmartCompare True: '2.22.4c' is newer than '2.5.4c' (because numerically, 22 > 5) '2.2a.4c' is older than '2.20.4c (because alphanumerically, '22.2a' > '22.20') '2.22.*' is SAME as '2.22.4c.3' (only when 2.22.* is from the compatibilty list) '2.22.4*' is older than '2.22.4c' (because '4*' < '4c', '4*' is never a wildcard!) With SmartCompare False: '2.22.4c' is older than '2.5.4c' (because alphanumerically, '2.22' < '2.5') '2.22.*' is older than '2.22.4c.3' (because '*' is less than '4') '2.22.4*.#' is older than '2.22.4.#' (because '*' is less than '.') Regardless of SmartCompare setting: '2.2a.4c' is older than '2.5.4c'. (because '2a' < '5') '2.22.blah' is newer than '2.22'
CaseSensitiveCompare	[boolean] The default value is False, no case sensitivity in version comparison. Applies to comparison of CompatibleVersions and Version INI variables with component property CurrentVersion.
CompatibleVersions	[string; comma-delimited; optional] A list of versions (in the same format as the version field) that this update can be applied over top of. If the user has, say, version 1.0.0.0 of your application installed, the patch may not apply. You may only want to patch 2.0.0.0 clients. Any person with a 1.0.0.0 client will have to upgrade to 2.0.0.0 before applying the update. If the SmartCompare INI variable is True, then you can use "wildcards" here. For example, CompatibleVersions=1.9.*,2.* would update all versions begining with '1.9.' or '2.'. Note that the '*' must be the only character of the segment in order to be considered a wildcard, and if it's not the last segment, then and trailing segments will be ignored. There is no wild card in '2.2*.3' or '2.*2.3'. Also, '2.*' is the same as '2.*.1'. This INI variable is optional. If missing, it is assumed that any version is compatible with the update, if its version compares older than the update.

Creating the Update ZIP File

When using the install action iaUseUpdate, you need to create a ZIP file containing the update and place that file on a web server for retrieval. This file should take on the same directory structure as your application. For example, if your directory structure looks like this:

MyApp (where your main executable is stored)
+ Samples
+ Help
+ Doc

then your update ZIP file should have the same structure so that you can place updated files directly over top of the currently installed versions. You may want to place a CHANGES.TXT file inside your update so that the user can view the release notes for the update some time after the update has been applied.

Localizing Message Strings

The AppUpdate component is easily localized to different languages. By default, the component has English messages linked into the component. If a different language is desired, the following actions must be performed:

1. Create a new DLL that basically contains nothing but a resource file containing a string table.
   Open the AppUpdateDE.DLL in a resource editor (like the Visual C++ IDE) and check out the string table that resides within that DLL for reference. If you would like the source to the AppUpdateDE.DLL file, e-mail me .
2. Open the AppUpdateMessages.RES file in a resource editor (to be used for comparison).
3. In the new string table, perform a one-to-one translation of all of the strings listed in the string table in AppUpdateMessages.RES. Each translated string should have the same resource ID as in the AppUpdateMessages.RES file.
   For example, translate the string "Update progress", which has a string ID of 100, to the equivalent foreign-language string, and give it the same string ID of 100.
4. Also copy the strings in the appropriate ZipMsgXX file into the new string table.
   For example, the german resource DLL AppUpdateDE.DLL contains within it the contents of the ZipMsgDE.RES file. You can get resource files for many different languages in the full version of the ZipMaster component, which you can download here.
5. Build the DLL and include it with your application distribution. Name the file "AppUpdateXX.DLL", where "XX" is the two character country code.
   For example, AppUpdateDE.DLL is for German translations.
6. Set the "ResourceDLL" property on the AppUpdate component that is contained within your form to the name of the DLL you just built.
7. Build your application and you're done!

Shortcut: A shortcut to the above procedure would be to copy one of the sample resource DLLs included with the AppUpdate component (e.g. AppUpdateDE.DLL) to a new file. Open the DLL in a resource editor and replace the resources in the DLL with your own translations.

Note: This technique of localization even allows you to change languages dynamically at run-time simply by shipping the appropriate resource DLLs with your application and setting the ResourceFilename property on the component.

Note: Unfortunately, the strings that are defined within the HTTP component and FTP component that are used by the AppUpdate component are not localized. Therefore, some rarely seen error messages may in fact appear in English even though you have localized the component for a different language. I will do my best to find a better, cross-language, HTTP and FTP helper component in the future.

Component Properties

PUBLISHED (Design-time/Run-time):

PUBLIC (Run-time):

Component Methods

Method Signature	Description
Initialize;	Make sure that this method is called before using the component within an application. If you want to override any design-time values you assigned to the component properties, assign the override values prior to calling this method. For example, your application may prompt the user for UserName, UserPassword, ProxyServer, and ProxyPort.
CheckForUpdate: TCynthesisAppUpdateError;	Call this method to check the web, FTP, or LAN/WAN server for an update. Note that for mode umAutoWithUI and umAutoNoUI, you call only Initialize and then this method. A good place to call this method is when your application is initializing. Another possible spot is when the user chooses a menu item in your application like "Check For Updates". Note that if you call CheckForUpdate and you are not on-line, the standard Windows dial-up networking dialog box will appear asking you to dial in to your Internet service provider. You may want to have your application check the on-line status and only call CheckForUpdate if you are on-line. If there is demand for this feature, I may add the check to the component itself.
DownloadUpdate: TCynthesisAppUpdateError;	Call this method once it has been determined that an update is available and the user has decided to apply it. This method should be called from the OnUpdateAvailable event handler in the case of a manual update.  Note that the "auto" UpdateModes will call this method for you.
InstallUpdate: TCynthesisAppUpdateError;	Call this method once the update file has been successfully downloaded and the user wishes to apply the update. This method should be called from the OnDownloadComplete event handler in the case of a manual update.  Calling InstallUpdate will trigger the update of the UPDATE.EXE helper application and resource DLL (if one is being used). The update of these files are necessary at this point as updating the helper application while it is running is not possible due to the files being loaded in memory. Note that the "auto" UpdateModes will call this method for you.
CancelUpdate: TCynthesisAppUpdateError;	Call this if for some reason you want to abort the update process once it has been started.

* For a definition of the TCynthesisAppUpdateError structure, see the file CynthesisAppUpdateTypes.pas

Component Events

Event Signature	Description
OnUpdateAvailable( Sender: TObject; versionInfo: TCynthesisAppUpdateVersionInfo)	This event is fired by the update component when an update has been found. The versionInfo object provides detailed information about the update that was found on the web server. This event allows the application to prompt the user to download the update, or dismiss the update until some later time. You should call DownloadUpdate once it is determined that the update should be downloaded. See the OnUpdateAvailable Event section for further details. If you are using umAutoWithUI mode and you do not furnish this event handler, the component will automatically prompt to download the update or cancel.
OnNoUpdateAvailable( Sender: TObject)	This event is fired when it is determined that no update exists on the web server. This may be because either an update info file does not exist, or because the version on the web server is the same or earlier than the one currently installed. This type of event is required since the whole update checking sequence is asynchronous. If it was synchronous, you could simply wait for a result code from the CheckForUpdate method. If you are using umAutoWithUI mode and have not supplied this event handler and no update is available, a messagebox 'No Update Available' will be presented to the user.
OnDownloadProgress( Sender: TObject; Progress: Integer; Msg: String)	This event is fired by the update component periodically to indicate the current progress and status of the update file download. The Progress parameter indicates a percentage complete, and the message is a status string that you may want to display in a status bar. This is a good place to update a progress bar based on the value, and display the message on a status bar. If you are using umAutoWithUI mode and have not supplied this event, the component will present a progress window with progress text and a progress bar for both downloads (info file and update).
OnDownloadComplete( Sender: TObject)	Called when the download of the update is complete. This is a good spot to warn the user that the application will now be closed and that the update will now be applied. You should call InstallUpdate once it is determined that the update is to be applied.
OnUpdateAborted( Sender: TObject; eReason: TUpdateAbortReasons)	This event is called when an error occurs when attempting to download the update or the update file. The error message will indicate the problem so you should display it to the user.. If you are using umAutoWithUI mode and have not suppied this event handler, the component will suppy its own and present appropriate error messages.
OnError( Sender: TObject; ErrorInfo: TCynthesisAppUpdateError)	This event is called when an error occurs when attempting to download the update or the update file. The error message will indicate the problem so you should display it to the user. - See AppUpdateTypes.pas for details on the TCynthesisAppUpdateError s structure

OnUpdateAvailable Event

The OnUpdateAvailable event is an important part of the TCynthesisAppUpdate component. This event is triggered in your code every time an update is discovered on the update server. The versionInfo object that is supplied as part of the event provides detailed information about the update. This information may be displayed in a dialog, on your form, or whatever you desire.

The update information that is available is described in the table below. Note that all of these values are pulled out of the update information file (INI) that is retrieved from the server during the update discovery stage (the call to CheckForUpdate).

Tips and Tricks

Here are some tips and tricks to help you out when using the component:

• Check out the sample application called AppUpdateTest - it will give you a good idea as to how the component works and what to do in the case of a manual update. It also provides a nice form that is displayed when an update is available. The form describes the update and provides a clickable link to the README file. Feel free to reuse this form (or a variation) in your own applications!
  
• The TCynthesisAppUpdate component will close your application automatically once the InstallUpdate method is invoked. This is to ensure that none of the application files are in use when the update is applied. Your application should be coded to expect this situation.
  
• The TCynthesisAppUpdate component will close your application automatically once the InstallUpdate method is invoked. This is to ensure that none of the application files are in use when the update is applied. Your application should be coded to expect this situation.
  
• Use the iaUseUpdate install action when you simply want to update certain files that have been installed to some file hierarchy in or under where your application's executable file is located. If you need to apply new registry settings, or install files to a different directory (e.g. under the Windows system directory), it is recommended that you write a small install program (e.g. using InstallShield) that does not permit any user interaction, but simply installs the files to the appropriate locations and adjusts the registry, etc. as required.
  
• It is recommended that every time you distribute an update for your application you update the main executable whether it needs it or not. This has the effect of updating the version number used by the update component to determine if an update on the web is newer than the one currently installed.
  
• When OnlineMode is set to olFTP, watch out for case sensitivity. The UpdateURL variable in the INI file, the INIUpdateURL property of the component, and the actual names of the file AND DIRECTORIES on the FTP server have to match perfectly, including upper-/lower-case.
  
• The update information file's extension does not have to be '.INI'. INI files tend to invite curious people to open them with Notepad. People are less apt to edit a file that is not obviously (by its extension) editable. You might want to use INF, DAT, UPD, etc.
  
• When using OnlineMode set to olLANWAN you can use a normal DOS-style path format (e.g. d:\path\filename) for the UpdateInfoURL property and a UNC format (\\machine\sharename\path\filename) for the UpdateURL INI variable, or vice-versa, or both values can be of the same format. Any UserName or UserPassword supplied will be used only with the UNC-formatted value.
  

Testimonials

• "I'd like to say that the CynthesisAppUpdate component is absolutely great - it's almost exactly what I've been trying to develop for use in a University project I'm busy developing. That's what I love about the delphi community - if you know where to look, you seldom have to re-invent the wheel, thanks to developers like yourself." -- James Burns-Howell
  
• "...truly wonderful component... NICE JOB!!!" -- Keith Pritchard
  
• "I recently discovered your magnificent AppUpdate Component for Delphi. It saved me hours of development and it really works great for me!" -- Timo Goebel
  
• "The CynthesisAppUpdate component has saved me hours of work and gives my applications that professional look. I'll be using it on all my Delphi projects from now on." --Michael Holligan

Acknowledgements

• Thanks to all the people who used the Beta version and provided me with comments/bug reports.
  
• Thanks to Francois Piette for creating the Internet Component Suite and making the source available free of charge.
  
• Thanks to Keith Pritchard for helping me work out the kinks in the distribution process for the Delphi 5 packages.
  
• Thanks to Timo Goebel for providing the German translations and Renato Portello for providing the Italian translations that are distributed as of v2.1.0.0.
  
• Extremely Special Thanks go to Shakya Jones for laying the groundwork and implementing a significant portion of the new features in v2.0.0.0 and later. The list of new features would not have been this substantial if it weren't for his valuable help. Great job Shakya!
  
• Thanks to Chris Vleghert and Eric W. Engler for creating the Delphi ZipMaster component that this component leverages.

James Waletzky,
[email protected]