wyUpdate can ensure users always have the latest versions of your software. Using the wyUpdate Designer you can manage & build your updates, as well as design how your update client looks and behaves. Once you've created your update, you can upload it directly to your ftp without leaving the wyUpdate Designer.The wyUpdate Client patches your files and handles Vista's UAC (User Account Control) to deliver the latest version of your software to your customers.
New Features:
- Manage past and future versions of your software
- Create patch updates (a.k.a. delta updates) for reduced bandwidth usage
- Undo and Redo all actions in the Designer
- Improved Designer and filetype icons
- Proxy settings overhaul
- Faster performance all-around.
- New destination locations for update files (e.g. Desktop, Start Menu, etc.)
- Can now create Desktop & Start Menu shortcuts
- The wyUpdate Client is now open source (C#)
Notable Bugfixes:
- The 'client.wyc' can now be included with updates
- Version numbers were parsed incorrectly
- The wyUpdate Client can now download from HTTPS sites with self-signed SSL certificates
- All registry types are now supported (binary data, 32-bit numbers, 64-bit numbers, etc.)
- The Files/Folders didn't remember their selection
- The wrong language was being built with the client.
- Update the Greek & Russian languages.
- Plus much more.
















I don't believe it's misleading. I spent most of my time talking about wyUpdate Professional, true, but I also mentioned Express and the differences between the two editions.
I'm not trying to bait and switch.
EDIT: Oh! You're talking about this post. Shoot, you're right. The title should be changed to "wyUpdate 1.0.1". The changes listed apply to the product as a whole (the Client and the Professional & Express Designers). I should have made the distinction clearer.
Last edited by Vorenus on 17 Oct 2008 - 15:51
My program, wyUpdate, is for developers. The developer has full control over the update creation and distribution to the user.
Now this is some, ehm... update check for developers not able to code an own one, right?
Here's a simple example, what if a user cancels the update right in the middle? A few files have been replaced, some registry keys edited. The program is now official corrupt. wyUpdate is smart enough to know what's been changed, and quickly rolls back to the last working version when the user cancels.
Plus there's the multiple administrative issues: What if your user is a limited user? Or they're using Vista UAC? Etc.
There are a whole bunch of subtleties beyond "File.Download()" and "File.Copy()".
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.