Override update site

Hi Andreas,

a) according to http://wyday.com/wybuild/help/override-server.php, you can override the server site used from wyupdate site by using the -server command line parameter:wyupdate.exe -server="http://example.com/server.wys"

However, that does not seem to have an influence on the update site.So my question: Is there a way to override the update site as well? Something like:wyupdate.exe -update="http://example.com/updates/"so that all .wyu-files are taken from the directory spedified here?

The update sites are contained within the server file (Along with other information to verify the authenticity of the update files). So you can only specify a different server site from the commandline.

Have you read the help topic on Update & Server Sites? It explains how you can specify some sites as server sites and some sites as update sites by right clicking the site (or leave the site its default as both server & update site).

Does this help? If not, could you explain what you're trying to do?

b) As stated in http://wyday.com/wybuild/help/commandline.php, you may add new version to your project file from an .xml filewybuild.exe "C:\YourProject.wyp" -add="newversions.xml"

Inside the .xml-file, the source of the files is given as absolute path. <Files dir="basedir"> <File source="C:\YourProduct\1.2\YourProduct.exe" /> <File source="C:\YourProduct\1.2\Awesome.dll">NewName.dll</File>Is there a way to use relative path names here (relative to the location of your project file)?

Relative paths will be coming in wyBuild 2.6.

Thanks for your quick reply.

> Does this help?

No not really.

> If not, could you explain what you're trying to do?

What I would like to do:

a) Use wyupdate for updates via internet (regular use case)server and update site: http://updates.mysite.com/mysoftware/

b) Use wyupdate for updates from local filesystem (somewhat unusual use case, but works like intended)server and update site: file://Documents and Settings/All Users/mysoftware/updates/

So I end up with the following:User that have internet connection can go with route a)route b (offline use case ): a zip-file containing server.wys and all *.wyu files is provided

My software would have a menu item "Import Update file" that allows users to choose a zip file containing server.wys and all *.wyu.This zip-file would be then automatically extracted to %COMMONAPPDATA%/mysoftware/updates/.Afterwards, I invoke programmatically "wyupdate -server %COMMONAPPDATA%/mysoftware/updates/server.wys" in order to automatically start the update process.

In order to make that work, the update site contained within the server file should be %COMMONAPPDATA%/mysoftware/updates/.However I cannot use the environment variable %APPDATA% fo the definition of the update site inside my wyupdate project, I can only a path like file://Documents and Settings/All Users/mysoftware/updates/. While this will work with XP, it won't work on a Vista or Windows 7 box that has a different %COMMONAPPDATA% path.

So I thought using something likewyupdate.exe -update="http://example.com/updates/"could maybe help in that situation.

Any ideas on that?

Your help is highly appreciated.

ThanksAndreas

Ok, I think I understand what you're trying to do. You're trying to do offline-updates, right? You're doing it in quite an interesting way.

We are going to be adding this to wyBuild in version 2.7, but in a much tidier way. You'll be able to create a patch *.exe that searches for & then installs patches for you.

wyBuild 2.7 is still a few months away, and the method you describe would require a major re-write of the update system without much user benefit. (Though, if you do want to hack the source you can).

Is a standalone patcher like I described what you're looking for?

> Is a standalone patcher like I described what you're looking for?

Yes, that's more ore less one of my requirements.

Exactly, that's what I would like to do: I would like to use wyupdate to distribute updates as previews to selected users only. Those updates are not meant as public updates for the majority of the users yet. I think I can handle that situation at the moment already by setting up a different combined server/update site for those preview updates and pointing my selected users to those preview updates by using the -server parameter of wyupdate.However, if a standalone patcher were available, I could handle that situation more elegantly by simply sending a patch_as_preview.exe out to my selected user(s).

Thanks for immediate response and keep on with your good work.

Andreas