Why not just use the %updatepath% variable and commandline switch?
[QUESTION/REQUEST] Add download site at runtime
Hello,first a question: when -updatepath and -server command line arguments are used with wyUpdate, if the update path or server are not accessible, does wyUpdate.exe try to use the predefined download sites specified when it was built?
If it does so all fine, but if it doesn't, I would like to suggest to add the ability to specify an additional update path and/or server path instead of completely overriding them.
Why? Say a user usually uses my application in a local intranet environment and I override update path etc to point to a local location to get updates. If that user then is traveling or is working from home, I still want the application to find updates over the internet.
I know, I could do this check in my application, but I think it's better if wyUpdate does all this.
Thanks
I think he wants it to auto-cascade from command-line back to project settings (if the command line location fails).
I think he wants it to auto-cascade from command-line back to project settings (if the command line location fails).
Exactly.
I've been thinking about this and I'm failing to see the broad application. If you have the ability to update locally, why wouldn't you prefer that?
That is, what's the benefit of adding a better download site to a list of (presumably) worse options?
I'll give you an example:
Say download sites in the wyBuild project has 2 download sites:1. %updatepath%\%file%2. http:\\XXXXX\%file%
Now, my application always calls wyUpdate.exe specifying -updatepath and -server commands. This tells wyUpdate to use the 1st download site. I do this because the application runs on multiple computers in a LAN and these computers may or may not have access to the internet so I use a locally available server for updates.
My question was whether wyUpdate falls back to download site 2 in case download site 1 (which is not a normal download site) fails. And what happens in case the location specified in the -server command fails?
If wyUpdate falls back to download site 2 then no problem for updates, otherwise that's where my suggestion comes into play as I still want a user to be able to update the application if not connected to the company LAN but internet access is available.I am still not clear though on what happens for the -server location even if this is the case.
Does it make sense?
My question was whether wyUpdate falls back to download site 2 in case download site 1 (which is not a normal download site) fails. And what happens in case the location specified in the -server command fails?
When a download site fails the next download site in the list is tried. When a new server site is provided by the -server argument then it overrides all server sites listed. So if the single server site fails then an error is shown to the user.
If wyUpdate falls back to download site 2 then no problem for updates, otherwise that's where my suggestion comes into play as I still want a user to be able to update the application if not connected to the company LAN but internet access is available.
So when a user is inside the company they get the updates from the LAN, when they're outside the company they get the updates from the publicly accessible website?
Yes
I have a question about -server and -updatepath. I use -server a lot. However just recently I've observed that for a new client even though it uses the correct -server path to get wyserver.wys apparently the redirect to get the wyu update file does not use the same server path. I simply fixed this with a new build for my client using their update server in the build instead of relying on the override. Is this what the -updatepath is for? I haven't touched my update code helper class in my application for years and it gets that information dynamically from data, so it wouldn't surprise me if this was new or a fix for the problem I am having.
Thanks. Also, good work as usual!
Trivia question: Is there a reason that (except for pathces wyu files) all the files start with wy* except the client? (e.g.wybuild.exe wyupdate.exe wyserver.wys, and client.wyc)