If you're using -updatepath, then there's no reason to use -server. However, -server is useful for companies that want to release to separate "channels". For example, a beta *.wys file and a stable *.wys file at separate locations on the server.
Are both -updatepath and -server arguments needed?
I'm a bit confused about the purpose of the -server commandline argument. If I've used the -updatepath argument, am I right in thinking that I don't need to use the -server argument as well? It'll be found using the specified path plus wyserver.wys?
If so then that's really all I need to know. Although, if anyone feels like explaining, I'm curious as to why, in that case, anyone would use the -server argument at all.
I actually thought about doing something like that, but I didn't think it would work:
Supposing I release a stable version 2, then I release a version 3beta, and a different server file for people who want to test beta versions. If I'm not resetting the updatepath, then I have to upload the updates for 3beta to the location were version 2 is.
Does that not mean that someone using version 1 who tests for a stable update, and is told that version 2 is available (from the 'stable' server file) would then end up updating to the 3beta update?
The *.wys file, if you double click it, you'll see it contains a list of all the download sites to the *.wyu files. So if you want to have "separate channels" make sure the *.wyu files don't overwrite old *.wyu files. Also, make sure the *.wys files don't overwrite other *.wys files.
Then, in your app, simply pass the correct *.wys file location to wyUpdate using -server (e.g. wyUpdate.exe -server="http://example.com/beta/wyserver.wys" ).