wupdate and subsiquent updates

[shares]

I've read the HOWTO: Add live Internet version updating to my program (http://www.lindersoft.com/forums/showthread.php?t=9459) and that cleared up a lot for me. But one question remains:

What if you were to do a version 3 of CoolApp. I create a new Web Update project and select which - the original version 1 or version 2?

Thanks

[linder]

We called it "Version 1" and "Version 2" in the demo to make clear what is
the "old" and what is the "new" version. In real life, most developers use
web update for the same version release only. For example, 1.00, 1.01,
1.02, 1.1, 1.2, 1.5, 1.6, etc. When a new major version is ready to ship, a
new installation with a new Product GUID is created and the new web update
supports again only this version. For example: 2.00, 2.01, 2.02, 2.1, 2.2,
2.5, 2.6, etc.

This is similar to the Windows update. A Windows Vista web update cannot do
updates for Windows XP nor can you use web update to update Windows XP to
Windows Vista.

But of course, it's completely your decision. You can do whatever you want.

A web update contains the incremental differences between the base version
and the revised version.

Let us assume the following scenario:

VERSION 1 (full install)
------------------------

file1 v1.0
file2 v1.0
file3 v1.0
file4 v1.0
file5 v1.0
file6 v1.0
file7 v1.0

VERSION 1.1 (web update)
------------------------

In version 1.1, you change file1 and file3. That means, your web install
for the web update only includes these two files.

file1 v1.1
file3 v1.1


VERSION 1.2 (web update)
------------------------

In version 1.2, you change file5 only. That means, your web install for the
update now includes three files

file1 v1.1
file3 v1.1
file5 v1.2

VERSION 1.3 (web update)
------------------------

In version 1.3, you change file1 only. That means, your web install for the
update includes again three files

file1 v1.3
file3 v1.1
file5 v1.2

Hope this helps.

Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[shares]

Thanks, I understand a web update is an incremental update, but my question is a little different.

I distribute v1.0. I create web update v1.1. During this process, I select the v1.0 sb project file. Ok, fine.

Now I need to create the v1.2 web update. Do I select the v1.1 or the v1.0 project file?

Thanks

[linder]

I think there is a misunderstanding here. You create the web update project only once. Then you modify this very same web update project file when you make a new web update available. When you select the "initial" v1.0 project file during the web update project generation then the wizard only copies the relevant information to the web update project (that is the Product GUID, product name, product version, etc.).

This is similar to your full install. You develop the v1.0 install project and I am sure you do not create the project for v1.01 from scratch, but you modify/enhance the v1.0 project.

Of course, you can create a new web update project for each and every web update you do. It's completely up to you. But it does not make much sense and is a waste of time.

Friedrich