Advice Required

[NewsArchive]

Needing a little advice here, so all comments welcome :)

Our webupdate at present includes product CHM and PDF files, which together
amount to nearly 30Meg. I have a full time person working on these so
changes are pretty much done on a daily basis. What I would like to do is
pull them out of the webupdate client, but I was thinking of adding a
question to the end of the webupdate which asked if the user would like to
download the latest product CHM and PDF files.

I'd like to know firstly if this is possible, and secondly what do others
do? I don't want to provide downloadable links to these files, as I would
like the downloads to be kept within a SetupBuilder exe.

Thanks in advance.

Colin.

[NewsArchive]

Hi Colin,

Well, we have the same problem. The CHM is 7.58 MB and the PDF is 18.9 MB.
Documentation modifications are done on a daily basis.

In your web update installation package, you can display a checkbox (e.g.
"Update Online Help and PDF"). If it is checked, download and update the
Help and/or PDF file (if new versions are available).

But I am playing with another idea. I have a small (100 KB) web installer
application that is executed from a "Update Documentation" menu item. If
the user clicks this menu item, the application starts the web installer
and it downloads and updates the documentation (but only if a new version
is available).

Friedrich

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

"point. click. ship" - that's SetupBuilder 5

[NewsArchive]

Thanks Friedrich, food for thought there and I think I'll try the first
option as I don't really want to add any more menu items to my application's
help menu.

I will have a play later :)

Colin.

[NewsArchive]

Hi Colin,

>Thanks Friedrich, food for thought there and I think I'll try the first
>option as I don't really want to add any more menu items to my application's
>help menu.

I would have a separate webinstall for the docs. That way you can
check for updates to the docs separately. What you can do is rename
the wupdate.exe for the doc update and then at the end of your web
update script, you can have a question to run the document update and
if the user choses to you run the other wupdate.exe for the docs and
it will download the documentation. I haven't tried this, but that's
the approach that I would try first:)

Best regards,

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


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Thanks Arnor, what I've chosen to do is alter my webupdate script to have 2
setup types, update without documentation and update with documentation and
this solves my issue real nicely :)

I guess I overlooked Setup Types when I did my webupdate script, I blame SB
for having too many good features :) lol