Hi.
Recently we upgraded from wyBuild 2.6.11.3 to 2.6.14.0. This solved a problem we had with wyUpdate.exe not working from behind a password protected proxy server (see separate thread on this issue).
However, this upgrade has appearantly created a new problem: Older versions of our software (still using wyUpdate.exe 2.5.25.0 from wyBuild 2.6.11.3) suddenly no longer accept the wyServer.wys file generated by the *new* wyBuild 2.6.14.0, thus preventing some of our customers from upgrading.
When trying to update (by calling automaticUpdater1.ForceCheckForUpdate()) - it fires the CheckingFailed event saying:
Error trying to save file: Error downloading "http://wyday.com/files/wyupdate/updates/client.wys": Unable to connect to the remote server
The same thing happens if I redirect the the automatic updater to look at a local directory holding the correct update files (by using -server and -updatepath in the command line arguments).
If I just replace the old wyUpdate.exe (2.5.25.0) with the new one (2.6.11.3), everything works like a charm.
Did you really break backward compatibility???
- Martin.
No, we take backwards compatability very seriously. I just tested again and wyUpdate 2.5 works fine with *.wys files generated with wyBuild 2.6.x. I also tested wyUpdate 1.0 and it checked for updates fine.
Error trying to save file: Error downloading "http://wyday.com/files/wyupdate/updates/client.wys": Unable to connect to the remote server
Are you sure this is not the proxy problem that the old versions have? The "Unable to connect" message has nothing to do with reading in the *.wys file.
Hi Sam, and thank you for your quick response.
Glad to hear that backward compatibility should be OK, which is also what I would expect. However the problem must then be something else - I'll have to do some more investigating here. I'm pretty sure that it used to work, so I'm a bit puzzled. I'll try to revert to wyBuild 2.6.11.2 and recreate update files and see for myself if those work or not.
I will revert to you with the outcome once I get so far.
Keep on the good work (and also your outstanding customer support).
-Martin.
