Webupdate docs - installer

[NewsArchive]

Hi Friedrich,

In pt. 3 in the "To create a WebUpdate installer:" section in "Using
WebUpdate in your Installation" you say:

...." We suggest you use the same Product GUID here." Hmm... Same as
_what_?<g> Do you mean that the PRoduct GUID should be the same as
for the install with the Webupdate Client?

Pt. 8:

"It's a good idea to add "Start Delayed File Install" ... around your
files"

Do you mean the "Install File" enries in the [ Install Files ] section
in the Script?

Pt. 16:

"Your application can now start wupdate.exe..."

Actually it can do that in pt. 8 in the previous section "To install
the WebUpdate Client" as at that point the wupdate.exe is included and
you need to be able to call it in order to use what comes next.

Now, I have put the main install into a download directory on my
server. I have also put it along with the config file into an
"update" directory on the server and intend to use it to download any
updates. The main download directory will be for the full install and
made available from my website, download sites etc. Does this sound
like a reasonable way to do this?

My plan is that the update installs will mainly contain updated exe,
help etc. where as the full install will of course include everything.


Best regards,

Arnór Baldvinsson
Icetips Software
San Antonio, Texas, USA
www.icetips.com

[NewsArchive]

Arnór,

> In pt. 3 in the "To create a WebUpdate installer:" section in "Using
> WebUpdate in your Installation" you say:
>
> ...." We suggest you use the same Product GUID here." Hmm... Same as
> _what_?<g> Do you mean that the PRoduct GUID should be the same as
> for the install with the Webupdate Client?

You are right. The Product GUID should be the same as for the install
with the Webupdate Client. Documentation updated.

> Pt. 8:
>
> "It's a good idea to add "Start Delayed File Install" ... around your
> files"
>
> Do you mean the "Install File" enries in the [ Install Files ] section
> in the Script?

Yes, but only if you have your files in the [ Install Files ] section.
Quite a few users have the files in one or more include scripts. In
this case, you can add "Start Delayed File Install" and "Stop Delayed File
Install" script function around the include scripts.

The Start/Stop Delayed File Install function makes sure all required files
are
downloaded before starting the installation/update/patch process.

> Pt. 16:
>
> "Your application can now start wupdate.exe..."
>
> Actually it can do that in pt. 8 in the previous section "To install
> the WebUpdate Client" as at that point the wupdate.exe is included and
> you need to be able to call it in order to use what comes next.

You are right. Changed in the documentation now, thank you.

> Now, I have put the main install into a download directory on my
> server. I have also put it along with the config file into an
> "update" directory on the server and intend to use it to download any
> updates. The main download directory will be for the full install and
> made available from my website, download sites etc. Does this sound
> like a reasonable way to do this?
>
> My plan is that the update installs will mainly contain updated exe,
> help etc. where as the full install will of course include everything.

Yes, this sounds good.

BTW, what I do is the following. Both full and update install images
(for Professional and Developer Editions) are located in the \SB5
subfolder on the server.

I have one script to compile the full version and one "update template"
to compile the updates. To generate the web updates, I use the update
template, create a new script and then start Auto Update Scan to let
SB5 generate the update script for me. I can now compile my WebUpdates
for SB5 Pro and Dev in 40-50 seconds.

Friedrich

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
1.954.252.3910

[NewsArchive]

Hi Friedrich,

>You are right. The Product GUID should be the same as for the install
>with the Webupdate Client. Documentation updated.

Thanks a bunch for all the info and updates:) I've got the updater
working on the client side so now I just need to figure out how the
updater works when pulling a new version:)

Best regards,

Arnór Baldvinsson
Icetips Software
San Antonio, Texas, USA
www.icetips.com

[NewsArchive]

Hi Arnór,

Thanks so much for all your suggestions :) I'll upload a new build very
soon.

Friedrich

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
1.954.252.3910