Why can not we include same files in different version.

Comparing version numbers is how wyUpdate knows there is a new version. Let's say your customers have version 1.0 and you release a new version "1.1". Half of your users update to version "1.1". Then, you change "1.1" with new files. The users who already updated to "1.1" (before you changed the files) won't see the "new 1.1". Only the users who haven't updated will see the "new 1.1".

So, to answer your questions:

• Yes create separate folders for separate folders.
• Create separate version numbers for changed versions of your app.

I understand your explanation. Thanks for that.But, we still prefer to have that feature, so that it will be easier for us to use your product.Other wise this is great product and but not that useful and a very tedious task to build and run updates using your product.

Is there any way we can build and update the files without creating new folder ?With out this feature this product is useless

You can completely automate the update creation process, see: Building from Commandline.

This way it's not a tedious manual process but rather an automated step that's part of your build release process.

Thanks for explanation.But we still can not use the same folder files for "build", we still have to mention new folder name.Correct ?

I'm not quite sure what you're trying to do. Are you just rebuilding the same version to re-test the update? Or are you building your version (let's say 1.1), some users update, then you rebuild 1.1 with new files, and some other users update?

Thanks again.

1. We have a process which runs once in a day, in turn it runs the "auto updater" everyday in the night.

2. When ever we finish (after QA testing or based on client requirement) last minute minor changes to the software, we rebuild 1.1 again with new files and upload.

4. Machines will get updated in the night thru OnceaDayProcess.

3. For sure we don't want to change the Version Number when we release the new files. If there is a Major change then only we change the Version Number.

Hope this makes sense.

Please help out.

Can you not add a sub or revision or patch indicator to your updates?

If your code for Tuesday is 1.1 and Wednesday it is also 1.1, then wyBuild has nothing to use to distinguish them.

However, if you have 1.1.0.0001 and 1.1.0.0002 (increment that final number on each day that you create a new build), then wyBuild has something to use.

Your software can still report to the user that it is 1.1 in both instances (it can even have it's resources marked as 1.1, though that might engender confusion).

But there needs to be something, even if only for the sake of wyBuild, that distinguishes these builds (and you'd need to keep the previous build files around for wyBuild to generate it's delta against).

\build\2011\06\22\build\2011\06\23etc.

I hope I'm not confusing you further. If so, my apologies!

thanks for explanation again.

I understand, and what you said. No confusion at all.

Again, my point is, irrespective of increase the "revision" number etc. we still need to create new folder copy the new files in that, in order to use your updater. Which we wanted to avoid this process of creating new folder and build etc.

Any solution..?

thanks

To make patches between versions (1.1.001 to 1.1.002, etc.) then wyBuild needs the files in separate folders so that it can actually compare the files. You can always automate this process. It doesn't have to be done manually.

Now, there is a way you can release updates by creating a single version inside wyBuild -- but this is not a patch. It includes *full* files for every update. For instance, if your application size is 20 megabytes when compressed then every time the user updates the user downloads 20 megabytes. So if you release an update every day for a year this will be 7.3 gigabytes (365 * 20).

If you're insterested in doing this "full files update" method, here it is:

• Create 1 version in wyBuild (e.g 1.1).
• Add your files to wyBuild.
• Build & upload the updates.

Then, for you next version:

• Rename the existing version in wyBuild (to something like 1.1.001)
• Overwrite the files that were on disk. And for any new files add them to wyBuild.
• Build & upload the updates

This way you don't have to create a new folder for every version of your software, but you lose the ability to create patches. THat's why we recommend always using the method described in the step-by-step walkthrough.