That's what I was looking for.
Thanks.
Ray Rippey
VMT Software
That's what I was looking for.
Thanks.
Ray Rippey
VMT Software
Yeah, I know how to do an auto updater. However, with the amount of
customers I have I don't even notify them if there is an update. There
is a page in my program where they can see any updates I've done and
what's in them. (I use a combination of jhtml and a help file I publish
online). So the folks that are interested in keeping up, they update all
the time, so I consider them my beta testers in a way.
I've made mistakes and created bad bugs.. not too often, but it's
happened. So if I were to notify everyone of an update and I had a bug,
there would be hell to pay. This way if there is a problem, I find out
about it and can fix it fairly quickly.
Ray Rippey
VMT Software
Ray,
from the technical point-of-view, you need two different GUIDs to register
the same APP with Windows multiple-times (this will generate different
uninstall and update entries). That's why you can only have one
installation of, say, the same Microsoft Word app version.
What about using the "Store Properties in INI File" option in "Install Web
Update Client". This "should" make the update process independent from the
registry.
But you have to make sure that your updater does not read installation
locations from "the other" app.
Friedrich
>Ray,
>
>from the technical point-of-view, you need two different GUIDs to register
>the same APP with Windows multiple-times (this will generate different
>uninstall and update entries). That's why you can only have one
>installation of, say, the same Microsoft Word app version.
GOOD point!
Thank you, Friedrich!
Wolfgang Orth
> from the technical point-of-view, you need two different GUIDs to register
> the same APP with Windows multiple-times (this will generate different
> uninstall and update entries). That's why you can only have one
> installation of, say, the same Microsoft Word app version.
>
> What about using the "Store Properties in INI File" option in "Install Web
> Update Client". This "should" make the update process independent from the
> registry.
That is how our custom SetupBuilder installers work.
At install time we modify the GUID of the application to be installed based
on the version of Clarion you are installing.
That is how our installers allow you to install:
ProScan for Clarion 9
ProScan for Clarion 10
ProScan for Clarion 11
Etc.
Each "product" can be uninstalled or updated independently of the others.
The also appear in Add/Remove programs as separate entries.
SetupBuilder rocks!
:-)
Charles
--
-------------------------------------------------------------------------------------------------------
Charles Edmonds
cjeByteMeSpammers@lansrad.com (remove the "ByteMeSpammers" to email me)
www.learnh5fast.com - Master building web and mobile apps with Clarion H5!
www.clarionproseries.com - ProDocument, ImageEx, ProScan, ProImage, ProPath
and other Clarion developer tools!
www.seal-soft.com - The xProduct Clarion templates - xWordCOM, xToolTip,
xDataBackup Manager and more!
www.ezchangelog.com - "Free ChangeLog software to manage your projects!"
www.setupcast.com - "A revolutionary new publishing system for software
developers - enhanced for SetupBuilder users!"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms - Now with PNG support!
www.fotokiss.com - "World's Best Auction Photo Editor"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
-------------------------------------------------------------------------------------------------------
There are currently 1 users browsing this thread. (0 members and 1 guests)