Web Update

[NewsArchive]

Suggestion:

I noticed if I check the "Enable Web Update" option and DO NOT
check the "Install Web Update Client" option the registry is not
updated with the application data. This is a FULL install script.

I had created my own version of wupdate.exe and was including it
in the files section from a folder other than [SB5_LIB]. It took me
awhile to figure out why I was getting an error when attempting to
check for updates from within my app.

Obviously I can work around this by modifying the INCLUDE
statement automatically placed in the script when the "Install Web
Update Client" is checked to the location of the wupdate.exe I want.

My suggestion is to either make this known in the docs or change
the RTL to add the registry information if "Enable Web Update" is
checked.

Thanks.

--
Regards,

Lee
http://www.cya2day.com

[NewsArchive]

Lee,

If the "Enable Web Update" option is checked, then the installer only
updates the version information only. In this case, the installer is a Web
Update Installer (to live update an existing application). But if a
previous installation did not initialize the web update feature, the
required registry entries are not available.

If both "Enable Web Update " and "Install Web Update Client" options are
checked, then the installer initializes the web update feature.

In SetupBuilder 5.6, we have renamed "Include WebUpdate Client" into
"Include and Initialize Web Update Client".

Friedrich

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

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

[NewsArchive]

Correction. It's (still) named "Include Web Update Client".

---
Andrea

Sales and Support, Lindersoft
www.lindersoft.com
1.954.252.3910

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

[NewsArchive]

Hi Friedrich,

I understand and I know how to work around my problem.

What I am suggesting is to include something in your DOCs
to inform your user that the necessary information to perform
Web Updates later WILL NOT be written to the registry UNLESS
the "Include Web Update Client" option is ticked.

In my case I did not tick this option because I was including my
own version of wupdate.exe from a folder other than [SB5_LIB] and
was including it in the files section not realizing that the registry
information would not be written.

Of course, when I attempted the Web Update later, I received an
error and had to examine the registry to discover there was no
information there from the initial install. Of course the Web Update
failed.

I expected it to be there because I checked "Enable Web Update"
and didn't realize it was the "Include Web Update Client" option
that actually invoked the writing of the registry entries.

Not sure this makes a whole lot of sense to you but it did have
me confused for a spell. In any event, I now know how to work
around it so it isn't an issue for ME any longer.

--
Regards,

Lee
http://www.cya2day.com

[NewsArchive]

Hi Lee,

Okay, I see. I'll add a note.

At the moment the doc says:

---

Initial Deployment

1. ...
2. ...
3. In the left pane, set the Enable iDeploy Web Update checkbox.
4. ...
5. In the left pane, set the Install Web Update Client checkbox. This will
automatically add the Include Web Update Client script function to the [
Modify System ] script section.

---

Thank you for your suggestion.

Friedrich

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

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

[NewsArchive]

Exactly....

Just a note to warn us that in order to use the Web Update in
the future the "Install Web Update Client" must be checked
in order for the registry information to be written.

--
Regards,

Lee
http://www.cya2day.com

[NewsArchive]

1) I have done Tools -> Options -> ftp profile. When I click the ftp
TOOLBAR BUTTON, I am told "You must enable the ftp upload feature..." but
not told where to do that.

2) The "Web Update" help topic ends "The only way to unlock the files is to
stop the application. Force the user to shut down the application and wait
in the middle of use was undesirable." That seems to be stopping in the
middle of a thought. Am I about to be told WHAT TO DO for that situation?

3) "Configure iDeploy Web Installation" topic: "Web Update Image"
[in] Mark this checkbox if your Web Update is a dynamic web installer. If
marked, you don't need to enter the above information.
WHAT is a "dynamic web installer"? How do I use that?

4) My web page does let visitors download the installation executable file
OR perform a web install. After a web install, the web update appears to
download EVERYTHING when there is a new version. I think I can follow the
instructions under Dynamic Scan and delta patch creation. I'm trying to
picture what would then be on the web.
a) My current install executable to download and run
b) Any needed delta patch files for (a)
c) My current web install that starts from scratch and installs everything
d) A web update version that makes needed changes only, similar to (b).

Now my problem: how do I keep track of (c) and (d) on my own machine, and
how do I keep them apart on my web site? In the case of (a) and (b) each
one is just a single file so naming is easy. For WEB install / update, sb5
takes over for naming everything. Is the answer to (3) above contained in
question (4)--it sounds as if I have to go from my current web installer to
a "dynamic" web installer situation. But I'm not finding instructions how
to sort that all out.

5) "Enable Web Installation" does not have a checkbox to encrypt my host
username and password. That must mean that the information does not become
part of my build on the web page. Then I'm not sure why I'm entering the
information in the first place; I have been uploading using other FTP
software.

6) To keep all versions the same, I think I should (a) ALWAYS check "Enable
Web Update" and "Install Web Update Client" even in the CD distribution
version, and then after that is debugged, (b) make an identical copy of the
project except this time check "Enable Web Installation" to make my 4(c)
above. To release my next version, I would perform these steps 6a-b for
that version AND AGAIN for the delta patch. Am I getting close?

I may just be having trouble reading the instructions... Maybe someone can
point me in the right direction.

--
Kent V. Busse, J.D.
www.acomputerwiz.com

[NewsArchive]

Kent,

> 1) I have done Tools -> Options -> ftp profile. When I click the ftp
> TOOLBAR BUTTON, I am told "You must enable the ftp upload feature..." but
> not told where to do that.

General Information -> Release Distribution -> Enable FTP Upload

> 2) The "Web Update" help topic ends "The only way to unlock the files is
> to stop the application. Force the user to shut down the application and
> wait in the middle of use was undesirable." That seems to be stopping in
> the middle of a thought. Am I about to be told WHAT TO DO for that
> situation?

Several options here. Display a message and ask the user to terminate the
application. Do this in a LOOP to make sure the user really terminated the
app. Not a good idea is to KILL the application (function is available in
the installer, but I would not use it).

We are doing this in our own installations (lines may wrap here):

Loop
Set Variable %SB5ACTIVE% to ScriptItem->Detect Active
Application(sbuilder.exe)
If %SB5ACTIVE% Equals "1" Then
Display Message Box "SetupBuilder (sbuilder.exe) is currently running.
...." -- "Application currently running"
Else
Break Loop
End
End

> 3) "Configure iDeploy Web Installation" topic: "Web Update Image"
> [in] Mark this checkbox if your Web Update is a dynamic web installer. If
> marked, you don't need to enter the above information.
> WHAT is a "dynamic web installer"? How do I use that?

You enable "Enable Web Installation" and "Enable Web Update". The first
option creates a dynamic web installer. If you don't use that option,
the compiler generates a single-file installer.

If you have several cluster files in your \Web folder (.00001, .00002, etc.)
then you have a dynamic web update package. If you only have one .exe in
your \Web folder, then it's a static web update package.

> 4) My web page does let visitors download the installation executable
> file OR perform a web install. After a web install, the web update
> appears to download EVERYTHING when there is a new version. I think I
> can follow the instructions under Dynamic Scan and delta patch creation.
> I'm trying to picture what would then be on the web.
> a) My current install executable to download and run
> b) Any needed delta patch files for (a)
> c) My current web install that starts from scratch and installs
> everything
> d) A web update version that makes needed changes only, similar to (b).
>
> Now my problem: how do I keep track of (c) and (d) on my own machine, and
> how do I keep them apart on my web site? In the case of (a) and (b) each
> one is just a single file so naming is easy. For WEB install / update,
> sb5 takes over for naming everything. Is the answer to (3) above
> contained
> in question (4)--it sounds as if I have to go from my current web
> installer
> to a "dynamic" web installer situation. But I'm not finding instructions
> how to sort that all out.

I think you have the Replacement Option (File Properties) set to ALWAYS,
right In this case, the installer downloads and replaces all files.
Not very "dynamic" <g> You have to set it to Check File (CRC).

> 5) "Enable Web Installation" does not have a checkbox to encrypt my host
> username and password. That must mean that the information does not
> become part of my build on the web page. Then I'm not sure why I'm
> entering the information in the first place; I have been uploading using
> other FTP software.

This option does not write anything to the registry son nothing to encrypt
here. Only the "Enable Web Update" option writes to the registry or an
INI file. If you create a web update image (Web Update Image set to Yes)
then you only have to enter the information once in the Enable Web Update
screen. All fields in the Web Installation Properties dialog are disabled.

> 6) To keep all versions the same, I think I should (a) ALWAYS check
> "Enable Web Update" and "Install Web Update Client" even in the CD
> distribution version, and then after that is debugged, (b) make an
> identical copy of the project except this time check "Enable Web
> Installation" to make my 4(c) above. To release my next version, I
> would perform these steps 6a-b for that version AND AGAIN for the
> delta patch. Am I getting close?

The version that makes your application "web update ready" always has
the "Enable Web Update" and "Install Web Update" options enabled.

Then, if you have a new version available, you only add the NEW files
to the web update package, never files that did not change since your
initial release.

For example, you have:

INITIAL RELEASE 1.0
-------------------
wupdate.exe (1.0)
File1.exe (1.0)
File2.dll (1.0)
File3.dll (1.0)
File4.dll (1.0)
File5.dll (1.0)

UPDATE 1.1
----------
In your update 1.1, File1.exe and File2.dll change. So you include
in the web update package:

File1.exe (1.1)
File2.dll (1.1)

UPDATE 1.2
----------
In your update 1.2, only File1.exe changes. So you include in the web
update package:

File1.exe (1.2)
File2.dll (1.1)

UPDATE 1.3
----------
In your update 1.3, File3.dll changes. So you include in the web update
package:

File1.exe (1.2)
File2.dll (1.1)
File3.dll (1.3)

The Auto Update Generator handles this for you. Select your first (initial
folder) and the latest version folder and it generates the script for you.

Does this help?

Friedrich

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

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