WyBuild fails to update behind a password protected proxy.

I just realized that my version of WyBuild (that's v2.5.18.0) fails to check for updates when I tell it to. The error I get is:

Failed to check for updates.Error trying to save file: Error downloading "http://wyday.com/files/wyupdate/updates/designer.wys": The remote name could not be resolved: 'wyday.com'

I think this is probably due to the fact that all the computers in my company access the internet through a password protected proxy server. Normally, when an application tries to access the internet using the default Internet Explorer proxy, it pops up a message box asking for the username and password. Unfortunately, however, WyBuild is not doing this and simply gives the error above.

It's not mission critical - since I can manually download and install updates even now, but it would be nice if one could perhaps store the username and password as part of the settings, or perhaps have it pop-up when the user manually initiates the update check.

That's a good idea. We'll add a proxy username and password entry for the wyBuild options.

On a related note, I was amazed that WyUpdate (the client side updater) manages to access the update site and download and install updates without me entering any information about the proxy server username and password anywhere. I don't really know how it accomplishes this, but it would be great if you could shed some light.

It depends on how your proxy is set up. wyUpdate just dumbly uses IE's proxy settings. Some complicated proxies restrict external sites with a user/pass, but allow internal sites unrestricted access.

So if you can download the update files unrestricted in IE, then you can download the update files unrestricted in wyUpdate.

Thanks for the information - but what you said about wyUpdate 'dumbly' using Internet Explorer's proxy settings brings to light a critical (but not difficult to correct) flaw in the updater. If the client's computer is connected to the internet - or to the update server - via a password protected proxy, then unlike most applications, wyUpdate will not prompt the user for a username/password, but rather, it will simply fail to connect...

This is really bad for situations like the one I'm in - where the clients will _always_ be connected to the internet via a password protected proxy...

Just a suggestion: you could get wyUpdate to prompt the user for a credentials when it fails to connect due to an 'Access Denied' error or something, and then cache the username/password and use it until the next time it fails to connect to the internet with an 'Access Denied' error - in which case, wyUpdate would try to connect without a username/password, and then prompt the user again if that fails. Or, you could include the username/password functionality via command line parameters or something...

Please let me know if there's a workaround or something - because it isn't too late for me to make changes to the update implementation yet...

If this makes a difference, what wyUpdate really does is 2 things: first it tries IE's proxy, then it tries again without IE's proxy. So if you have a password protected proxy it's failing to download the files, then it tries again without the proxy and it's either succeeding or failing.

At any rate, you can overwrite the default proxy and use a password protected proxy by passing wyUpdate.exe the following commandline arguments:

wyUpdate.exe /proxy:"http://proxyserver:80/" /proxyp:"PASSWORD" /proxyu:"USERNAME" /proxyd:"OPTIONAL_DOMAIN"

Ok we've uploaded the Proxies in wyUpdate help document.

Works like a charm... thank you so much!