Incremental update confusion

according to this linkhttp://wyday.com/wybuild/help/faq.php#in_client_wyc

client.wyc does not contain the list of files

so can i fake the client.wyc build?

The client.wyc files contains the version of your app. wyUpdate uses that information to download the correct *.wyu file.

can I modify the client.wyc file with out the wyBuild project?

I mean I need to change the client.wyc automaticly.

Every time I change my development version. The client.wyc should be modified too...(I added the client.wyc file to my solution so after build my NSIS setup includes the client.wyc file)

Is there an easy way for this?

Or should I follow this code and made a small console app to change client.wyc.http://wyupdate.googlecode.com/svn-history/r129/trunk/ClientFile.cs

can I modify the client.wyc file with out the wyBuild project?

No, you shouldn't. wyBuild takes care of all the details. If you start doing this yourself then you'll miss something when we improve wyBuild. Just use the wyBuild automation to build wyUpdate.exe and the client.wyc file.

When using wybuild.cmd.exe I guess we can copy the necessary 2 files and it works, does it needs anyting else?

* wybuild.cmd.exe* Controls.dll

In my situation we have a powershell script that increments our verison.

Our aim is changing the client.wyc in every build. but we want to change the servers files when we will make a release...

Is it ok to using a small xml like the one below... because we are just going to change the client.wyc.. ?

<Versions> <AddVersion> <Version>5.3</Version> <Changes>Some very very cool stuff</Changes> </AddVersion></Versions>

And for every developer's machine do we need to buy a license as they are just going to use the wybuild.cmd.exe ?

and one more question.

If our client.wyc has "5.3" and the server has "4.3" will it downgrade itself?

thanks for your help.

When using wybuild.cmd.exe I guess we can copy the necessary 2 files and it works, does it needs anyting else?

Install the full wyBuild. Don't pick and choose files or things will crash (and you'll get other odd behavior). The wyBuild installer isn't very big (especially in 2012). It's currently under 2 megabytes.

Our aim is changing the client.wyc in every build. but we want to change the servers files when we will make a release...

I can't for the life of me figure out why you would want to do that. wyBuild takes care of making the patches. You shouldn't try to do this manually.

And for every developer's machine do we need to buy a license as they are just going to use the wybuild.cmd.exe ?

Yes.

If our client.wyc has "5.3" and the server has "4.3" will it downgrade itself?

No.

>

Our aim is changing the client.wyc in every build. but we want to change the> servers files when we will make a release...>

> > I can't for the life of me figure out why you would want to do that. wyBuild takes> care of making the patches. You shouldn't try to do this manually.

our testers can re-installs our app after every build... every build prepares a new setup. this is an automated process we need to automate the client.wyc versioning.because at app startup it checks for updates and downgrades the app automatically...

we missed a question in the previous post.

Is it ok to using a small xml like the one below... because we are just going to change the client.wyc.. ?(no files included..., it seems working like this but I want to be sure...)

<Versions><AddVersion><Version>5.3</Version><Changes>Some very very cool stuff</Changes></AddVersion></Versions>

That should work.