question about product and upgrade GUID

[NewsArchive]

So, after creating a new folder(s) for all my c11 stuff (the install
gets the files out of these new folders)... should I go ahead and change
both the product guid and the upgrade guid? I obviously don't want my
upgrade to have all of the runtime dll's from the old software so I
assume I make my update install to match with the new upgrade guid?

Also, it seems I'll have to create a new update ftp folder.. and the
customer with the older version.. will have to completely reinstall the
program so they can get updates from the newer ftp folder.. right?

Just want to make sure I'm not missing anything here.

Thanks,

--
Ray Rippey
VMT Software

[NewsArchive]

Also, I looked at my product guids and they all matched.. but the
upgrade guids didn't match at all... I am assuming as long as the
product guids are all the same (I have a demo install, a normal install,
and an update install)... the update guids don't matter?

Thanks again,


Ray Rippey
VMT Software

[NewsArchive]

Ray,

if your "new" and your "old" releases should co-exist on the same machine,
then you need a new unique Product GUID in Windows. You'll also need a new
update project for your web updates in this case. Similar to SoftVelocity's
Clarion 9, Clarion 10, Clarion 11.

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.

Friedrich

[NewsArchive]

While I am replacing the installation... I'm thinking that I don't want
the new clarion dll's and 3rd party dlls in the update... so the update
would be smaller. I would then have to do an actual install first, to
override all the old dlls, so then the next updates would be small.

I could make an update that had all the new dlls in it... if it were
possible that the next update after that could come from a different ftp
folder.. and be a smaller one without the new dlls. Kind of tricky if
possible. I think I tried this before and I never got it to work.. had
to go with a new install.

What is the upgrade guid used for?

Ray Rippey
VMT Software

[NewsArchive]

Friedrich,

>
>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?

Wolfgang


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.

Friedrich

[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]

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]

I think the update won't work.. My main installation and my update
install both have the same product guid. I'm going to change it for my
new stuff. I have decided to create a new ftp folder, a new install, and
a new update with new guid's. My customers will have to 'install' the
new program once, then it will use the update install after that. The
reason for this is to make my update install small.. it won't have any
runtime dlls from clarion or 3rd party. If a 3rd party updates and I
have to distribute the new dll... then I'll just add it to both installs.

While making my new ftp folder for updates, I realized the old one was
created in June of 2015. I did the same thing back then, made the
customers get a new install. 4 years of clarion10.. pretty good. I hope
it's the same for 11, because this was a real PITA!

Ray Rippey
VMT Software