Was this happening before? Is "-updatepath="http://..." " still set in the wyUpdateCommandline property when you press InstallNow?
Strange behaviourSolved
Hi Wyatt, I need your help on this:
You may recall from this previous thread (https://wyday.com/forum/t/191/my-app-will-not-update-updatepath-automaticupdater/#post-933) that I use command line parameters to override the updatepath.
You then located a bug and fixed it in version 2.5.24. Now I use version 2.5.25, and everything works fine - almost!
Scenario:
I have foreseen the update url to be:
http://update.myupdatesite.com/procuctname
but I have not yet established a server on the Internet with that address.
However, for testing purposes, I connect a test web server to my local network, and I cheat my Windows machine (Windows XP SP2) into finding it by adding the following entry into the c:\windows\system32\drivers\etc\hosts file:
"192.168.0.102 update.myupdatesite.com"
This makes in fact my app discover the update, and my app presents to me the release notes for the next version and offers me to upgrade - everything ok so far. But, when I click the "install now" button in my app and wyUpdate attempts to read the update files from the web server, I get the following exception:
"Could not parse the URL "%updatepath%/product.demoreleasea.to.demoreleaseb.wyu" - it's either malformed or is an unknown protocol."
Again it seems that the %updatepath% variable doesn't get properly expanded by wyUpdate.exe.
But here comes the strange part:
If I pull out the internet network cable from my router (the one from my ADSL-modem supplying internet to my local network) and repeat the whole thing, my app updates like charm from the local web server! How can that be?
Could you please investigate or tell me why the hosts-file trick doesn't do the job properly while the internet cable is connected?
- Martin
What do you mean with "before"? I belive it has always been this way, but it's the first time I use the hosts-file trick to access the local server. In real-world, however, when the update server is really present on the Internet, there seems to be no problem at all.
My app works like this: When AutomaticUpdater fires the UpdateAvailable event I show a dialog to the user presenting him the release notes for the next version and an "InstallNow"-button.
The event handler of the button then calls the automaticUpdater1.InstallNow() method, and at that time the automaticUpdater1.wyUpdateCommandline property shows:
-updatepath="http://update.myupdatesite.com/myproductname" -server="http://update.myupdatesite.com/myproductname/wyserver.wys"
And this is the case *both* when the internet cable is pulled out (and the update succeeds) and when the cable is connected (update fails with "malformed URL"-exception).
I believe it should be fairly easy for you to reproduce this behaviour.
-Martin
I haven't been able to reproduce this. Can I see your download site list in your wyBuild project? A screenshot will do (send it to support@wyday.com ).
Hi Sam.
I have now posted a small example project to support@wyday.com. Hopefully you can now see the error for yourself.
-Martin.
I got it. I'll try to reproduce it now.
Great!
Just an update: I can reproduce this - I'm trying to track down the cause.
Even more great!
Hi Sam.
Just wondered if there's any progress in this case?
- Martin
Yes, this will be fixed in wyBuild 2.6.7. We're trying to get this released by the end of this week (9/17).