question about product and upgrade GUID

[NewsArchive]

>Wolfgang,
>
>If you're curious, you can look in the registry and see how the GUID
>is used with the add/remove programs Windows feature. (See pic.)
>
>This is also why my screen shot shows two separate uninstall items
>for SB8 and SB10 on this machine. (They have different GUIDs).
>

What a cute name you have choosen for your program! I had to laugh out lod.

Sha-Too

Gesundheit!


Regards,
Wolfgang Orth
www.odata.de

Please note:
From time to time it happens, that I overlook a reply to my postings.
Please don't be angry.
In case of an emergency, try to contact me via mail.

Bitte beachten:
Von Zeit zu Zeit passiert es mir, dass ich Antworten auf meine Postings übersehe.
Bitte nicht böse sein.
Im Notfall bitte Kontakt per Mail versuchen.

[NewsArchive]

>Wolfgang,
>
>>>If it is an update (which replaces the existing installation), say, an
>>>update from 10.0 to 10.1, then don't use a separate Product GUID.
>>>
>>
>> what happens if we do?
>
>from the technical point-of-view, you register a NEW application (product)
>with Windows. It will create a separate uninstall entry in the Program and
>Features panel.

Hm

Hmmmmmmmmm

Hmmmmmmmmmmmmmmmmmm

Lets say, I have a program version 5.0.

Now I publish this program as version 5.1.

For existing installations, I want to provide an "update-installer", which
lifts the existing installed version 5.0 to version 5.1. This
"update-installer" does not contain any table, which is individual to the user,
like licence, but also that daily work stuff (Bewegungsdaten, whatever this is
translated into english).

They all have to have the same GUID?

I know that it a clumsy and pedestrian way to have a separate
"update-installer" to avoid overwriting existing data, because in SB I can
exclude all those files from being replaced. But in the past it happened that
admins made mistakes on their side, blaming it was my fault. So I separate
these two installers, with the result that the programs from the
"update-installer" are not able to run, if not installed over the existing and
licensed version. (Maybe I have to rethink my strategy).

Work could be so easy without customers....

Regards,
Wolfgang Orth
www.odata.de

Please note:
From time to time it happens, that I overlook a reply to my postings.
Please don't be angry.
In case of an emergency, try to contact me via mail.

Bitte beachten:
Von Zeit zu Zeit passiert es mir, dass ich Antworten auf meine Postings übersehe.
Bitte nicht böse sein.
Im Notfall bitte Kontakt per Mail versuchen.

[NewsArchive]

Hi Wolfgang,

> Hm
>
> Hmmmmmmmmm
>
> Hmmmmmmmmmmmmmmmmmm
>
> Lets say, I have a program version 5.0.
>
> Now I publish this program as version 5.1.
>
> For existing installations, I want to provide an "update-installer", which
> lifts the existing installed version 5.0 to version 5.1. This
> "update-installer" does not contain any table, which is individual to the
> user, like licence, but also that daily work stuff (Bewegungsdaten,
> whatever this is translated into english).
>
> They all have to have the same GUID?

Yes, that is correct! In this case, 5.0 and 5.1 have the *same* Product
GUID.

Friedrich

[NewsArchive]

It's a big hit at the peppermill convention.

Jeff Slarve
www.jssoftware.com

Ones and Zeros are my Heroes

[NewsArchive]

Danke!

That was a test of dual/SHA-2 code-signing with my 2014 certificate
(before Friedrich made it as transparent as it now is).

I went back to an old machine to find something with a registry entry
so I could make the screen shot.

jf

[NewsArchive]

Hi Wolfgang,

> They all have to have the same GUID?
Yes. It's the same PRODUCT, even if you have different versions. For
example Setup Builder is one product even if it's in many versions.

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC

[NewsArchive]

Hi Ray,

> In my case.. there is only one program on the machine. The new one
> overwrites the old. However, My thinking is I want a different guid and
> install because I don't want people with the old program (and it could
> be several versions old), updating to the new (update) one.. because the
> new 'update' doesn't have the runtime dlls from Clarion and 3rd party...
> so they have to first install the new install over the top.. from then
> on out, the updates come from a different ftp folder.

I include everything in the update, not just "updated" files. That way
you can have version 1 and you can still update to version 10 (or
whatever) I.e. my full install and my web install/update are
essentially the same, just one is in a single EXE, the other is on the
web and needs the SB web update thingamajigger to update I have used
this with both client software and my own, although with my client
software the update does NOT include a separate Crystal Reports
installer that only the full install includes. Other than that, it's
the same.

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC

[NewsArchive]

Yes, I thought about that... but I want my update to be smaller... my
main install is around 60mb, and my update is around 24mb. Not that much
smaller in this day and age I guess. But I do have clients that live way
out in the boondocks and their internet is slow.. so it makes a
difference for them. Plus, if I miss something.. I can go back to the
Clarion10 stuff if I have to. I leave the file structures the same for a
few versions so I can revert. Not that it happens often, but sometimes
I've had an update go haywire... especially when upgrading versions of
Clarion.

What would be really nice, is create a last update for my clarion10
project that would cause my new install exe to install. Or, maybe I'll
make one last update to the software that has a link to the new
install... that sounds easier.

Ray Rippey
VMT Software