%versionfrom% (Incremental patching)

hello

im trying use %versionfrom% for my updated folder and in the serverfilename.

its not working .. if i dont get error.. the file or folder have %versionfrom% in it.

The server files don't support version variables at all (neither %versionto% nor %versionfrom%). You can use %versionto% in the path for the output folder:

[attachment=0]Properties.png[/attachment]

Why do you want to use %versionfrom% in the output folder?

trying use this to solv a problem I have

my app is at v1.0 (when i start it say up to date)i create v1.1 and v1.2 (my problem is that I have 2 server file at same name) so after upload patch 1.2 people cannot update from 1.0 to 1.1

i have try create update folder with %versionto% its working well but how my app can know the new update and server file are in 1.1 folder

thats why i try use %versionfrom% and create the next patch in the actual app version folder, but this crate %versionfrom% folder

this way my patch v1.2 will be in folder 1.1

thanks

I don't quite follow what you're saying. Are you trying to limit people running 1.0 of your app from running 1.2 of your app? Or are you saying people running 1.0 of your app can't update to 1.2?

no, i want everyone always update to latest version

but i dont want upload all my project everytimeim not using catch all update

how client know there is new update, if this update is in new different version folder ?

what will be my download site to match the folder?

"http://www.mysite.com/update/%versionto%/%file%

Ok, well the good news is that wyBuild handles all the details. The update file locations are stored in the "server.wys" file. wyUpdate downloads this server.wys file and automatically determines which update file to download.

The file locations on the server are determined by the file site:

[attachment=0]wybuild.site.png[/attachment]

So you would upload the server.wys & all the update files to the "updates" folder on your site's ftp server.

Regarding the many files being built everytime you build your updates, realize that the update patches are built for all previous versions to the latest version. That is:

1.0 to 1.2and1.1 to 1.2

This way each person that updates will download the smallest possible patch file to get to the latest version (1.2 in your case).

Thats my problem .. I dont want my user able to get the fastest way to get my update. sound weird but there is a reason. Maybe there is a better way to accomplish this.

if I have 4 version (1.1 1.2 1.3 1.4)i want user download version 1.1 to 1.2 and then 1.2 to 1.3 ... maybe download all available version and install them in good order.

when i create new patch 1.2 to 1.3 the server.wys change and 1.1 user cant update to 1.2if i create 1.4 patch the server.wys change and 1.1 and 1.2 user cant update

I cant create a patch to include all other patch...the program is big and i dont want upload everything all the time.

there is a way to make all to current version make patch (1.1 to 1.2) (1.2 to 1.3) (1.3 to 1.4) and create server.wys for those patch

in wybuild I must include all file of program in each version or only the file that have change or added?if i have a big file 1gig, the updater can update it without replacing it ?

thanks

Thats my problem .. I dont want my user able to get the fastest way to get my update. sound weird but there is a reason. Maybe there is a better way to accomplish this.

The reason we build updates like "X to Latest" (where X is all your old versions) is that it generates the smallest possible files. This makes the upload a bit larger, but it will save you bandwidth costs in the long run. Because instead of downloading "X -> Y -> Z -> Latest" the user just downloads "X -> Latest" which will be a considerably smaller load on your servers.

if I have 4 version (1.1 1.2 1.3 1.4)i want user download version 1.1 to 1.2 and then 1.2 to 1.3 ... maybe download all available version and install them in good order.

when i create new patch 1.2 to 1.3 the server.wys change and 1.1 user cant update to 1.2if i create 1.4 patch the server.wys change and 1.1 and 1.2 user cant update

I cant create a patch to include all other patch...the program is big and i dont want upload everything all the time.

If you want you can exclude the "Catch all update". This file is considerably larger than the patches (because it contains full files.) Just go to the project properties and uncheck "Create a catch all update for corrupt installations".

there is a way to make all to current version make patch (1.1 to 1.2) (1.2 to 1.3) (1.3 to 1.4) and create server.wys for those patch

No. wyBuild doesn't build incremental patches. This method is inefficient and increases the file size considerably.

another question : in wybuild I must include all file of program in each version or only the file that have change or added?

Include every file. wyBuild automatically scans the differences and excludes files that are identical, generates tiny patches for files that are different, and adds/deletes new files or removed files.

The patching should succeed. Tell me if that works.

im testing with 100 megs project

i have try patch version 1.0 to 1.1 uploading atm

next update will be 1.1 to 1.2 already done ..( have patch a big file with a small fix ) the patch 1.1 to 1.2 is small and 1.0 to 1.2 its full size program.

I guess it will work .. but I must upload my complete program each time I create new update. Later it will maybe be 2gig or something.

There is a way to lower the upload time ?There is a way to update/reuse the old patch file on ftp server ?

thanks

edited : i have encounter error failed adler error while downloading big patch file. Just clicked retry now and download continue... and stop again with adler error .. click again retry now and continue .. and have done this 4-5 time for a 100 megs update. at the end .. the patch is working.

using automaticupdater.dll, im missing something in my c# client loader?I use client loader to patch the client before start it.

edited for test result : 1.0 to 1.1 workedI have upload the new patch 1.0 to 1.2 and 1.1 to 1.2Updating 1.1 to 1.2 was OK. updating 1.0 to 1.2 (cant test it right now.. webhost down :S)

i will post new result of 1.0 to 1.2 and another test 1.2 to 1.3 (but look like it work this way)

if my update was not on webhost there will be no upload problem.but like you say... save bandwith at the end is the most important!

Question : What is the best way to make a quick fix update, without uploading the whole project ?Not using inclemental patch ... there is a way to do something like this ?example .. have 1.1 - 1.2 - 1.2.1 - 1.2.2 - 1.2.3 - 1.3 - 1.4 - 1.5 - 1.5.11.1 full update include 1.0 to 1.11.2 full update include 1.0 to 1.2 and 1.1 to 1.21.2.1 -1.2.2 - 1.2.3 quick fix - no need to upload whole project1.3 full update that include all other version1.4 full update1.5 full update1.5.1 quick fix...

thanks

im testing with 100 megs project

i have try patch version 1.0 to 1.1 uploading atm

next update will be 1.1 to 1.2 already done ..( have patch a big file with a small fix ) the patch 1.1 to 1.2 is small and 1.0 to 1.2 its full size program.

I guess it will work .. but I must upload my complete program each time I create new update. Later it will maybe be 2gig or something.

There is a way to lower the upload time ?

Do your 1.0 and 1.1 versions have wyUpdate included with them when you released them to your users? If not, then there's no point in building updates from these versions. Just start with the first version that includes wyUpdate.

There is a way to update/reuse the old patch file on ftp server ?

No. You can delete the previous updates when you release your new update.

edited : i have encounter error failed adler error while downloading big patch file. Just clicked retry now and download continue... and stop again with adler error .. click again retry now and continue .. and have done this 4-5 time for a 100 megs update. at the end .. the patch is working.

Does the update file fail adler validation or does the patching fail? If the update download fails then make sure you always upload the latest server.wys file on your ftp server. If the patching fails then something else is wrong.

using automaticupdater.dll, im missing something in my c# client loader?I use client loader to patch the client before start it.

I'm not quite sure what you mean.

Question : What is the best way to make a quick fix update, without uploading the whole project ?Not using inclemental patch ... there is a way to do something like this ?example .. have 1.1 - 1.2 - 1.2.1 - 1.2.2 - 1.2.3 - 1.3 - 1.4 - 1.5 - 1.5.11.1 full update include 1.0 to 1.11.2 full update include 1.0 to 1.2 and 1.1 to 1.21.2.1 -1.2.2 - 1.2.3 quick fix - no need to upload whole project1.3 full update that include all other version1.4 full update1.5 full update1.5.1 quick fix...

Are the patch files really as big as the full project? If you've added the files correctly to wyBuild then the patches should be an order of magnitude smaller than the source files.

Do your 1.0 and 1.1 versions have wyUpdate included with them when you released them to your users? If not, then there's no point in building updates from these versions. Just start with the first version that includes wyUpdate.

version 1.0 1.1 ... 1.5 of my project is only for testing the update process ... there is some specific difference between them to know is update good.

Does the update file fail adler validation or does the patching fail? If the update download fails then make sure you always upload the latest server.wys file on your ftp server. If the patching fails then something else is wrong.

adler validation, and I always upload the wyserver generated for the update I uploadeverything is in same folder: Updates\%versionto%

Are the patch files really as big as the full project? If you've added the files correctly to wyBuild then the patches should be an order of magnitude smaller than the source files.

I want my first update the full project .. and then able to make update without uploading the full project when I create update (create new wyserver.wys)

Sometime I want be able reupload the full project because lots of tiny update or big major change.

I give a clientloader to my user.My user start the update processthe update 1.0 to 1.1 - 2gigs(maybe give the full program right away... but maybe later i can have really big update)(im using 100 megs project for testing)

file on server:mygame.1.0.to.1.1.wyu (100 megs)wyserver.wys

if i create a little patch 1.1.1 (2megs)

file on servermygame.1.0.to.1.1.1.wyu (102 megs)mygame.1.1.to.1.1.1.wyu (2 megs)wyserver.wys

to create a little 2 megs patch ... i must reupload the whole project (100 megs for test)

mygame.1.0.to.1.1.wyuis now this filemygame.1.0.to.1.1.1.wyumust reupload it, thats what I dont want to do!

but there is a tiny patch 2 megs (1.0.to.1.1.1)

maybe you have a idea to manage my big update, something parallel, working with another wybuild project ?

** Sorry for my english, is not my first language

.. I can send you my clientloader if you want try it ..

thanks

If the downloading fails due to adler validation failing then either the webhost is flaking out, or you're not uploading the *.wys file with the *wyu files. (The *wys file contains adler checksum of the wyu files. So you must upload both the server files and wyu files.)

As far as incremental patch goes, I can see why you want it. Uploading 100 megs everytime you create even a small fix is quite a long upload.

We'll consider adding it to future version. But as it is now you'll have to upload all the update files every time you create a new update.

Thanks you Wyatt for your help. I will use this for my project.

Good to ear ... We'll consider adding it to future version ...

Meanwhile I will give full game and clientloader with installer ... and just add or remove file to project with wyUpdate.

------------------

Maybe is the webhost problem for adler validation. I always upload *.wys file with the *.wyu patch.Maybe is the ftp transfer.I will do some other test, and another topic about it if needed.

As far as incremental patch goes, I can see why you want it. Uploading 100 megs everytime you create even a small fix is quite a long upload.

We'll consider adding it to future version. But as it is now you'll have to upload all the update files every time you create a new update.

Hello

Any news about incremental patching?

Thanks

wyBuild 2.7.0 will have it. It's coming after wyBuild 2.6.18.