Delayed File Installed

[NewsArchive]

What is the correct approach to using the Start/Stop Delayed File Install when
I am including a script to install MSDE and thereby seperating the file
installation into two different areas?

Greg Fasolt
G. Fasolt and Associates

www: GFasolt.com S.M.

[NewsArchive]

Hi Greg,

No need to use "Start/Stop Delayed File Install" in standard installations.
I would suggest to use this for web updates only - it makes sure that files
are only replaced after all files have been downloaded successfully.

Friedrich

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

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

[NewsArchive]

Hi Friedrich,

Thanks for your reply. Unfortunately, I still have questions.

I have selected both the Web Installation and Web Update options in my SB
project. Is this acceptable or do I need to create two projects? Should I be
using "Start/Stop Delayed File Install" in this case? If so, should it be
controlled conditionally based upon install vs. update, and if so, how?

Greg

Greg Fasolt
G. Fasolt and Associates

www: GFasolt.com S.M.

[NewsArchive]

Hi Greg,

I am here to help ;-)

If you have selected both the Web Installation and Web Update options in
your SB5 project, the compiler generates a Web Installation (instead of a
single-file exe) and "initializes" the Web Update technology. BTW, this
will *not* generate a web update!

In the above case, I would use "Start/Stop Delayed File Install" only if
this is an update (if you update or replace an existing application) or
if your web installation replaces existing files (e.g. Windows system
files). If it is a new installation and the installer does not replace
existing files, there is no need to use the "Start/Stop Delayed File
Install" feature.

Does this help?

Friedrich

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

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

[NewsArchive]

Hi Friedrich,

I'm beginning to get a grip on this, but I believe I'm still weak on some basic
concepts. If you can direct me to the proper topis(s) in the help document,
that would be fine -- I just can't seem to find the answers.

Additional questions within the context of your reply, below.

Thanks again,
Greg

>Hi Greg,
>
>I am here to help ;-)

And I am grateful. SB is a great tool, a far better experience than any of the
3 or 4 installer tools I've used - I seem to be the weak link right now.

>
>If you have selected both the Web Installation and Web Update options in
>your SB5 project, the compiler generates a Web Installation (instead of a
>single-file exe) and "initializes" the Web Update technology. BTW, this
>will *not* generate a web update!

I assumed that, by configuring mt SB project in this way, that I would be
creating the Web Installer. I also assumed that once a user installed my app
using this installer, that I could increment the Product Version, and produce a
new Web Installer that would automatically support the Web Update when the user
executed wupdate.exe from the installed app. Is this not correct?

>
>In the above case, I would use "Start/Stop Delayed File Install" only if
>this is an update (if you update or replace an existing application) or
>if your web installation replaces existing files (e.g. Windows system
>files). If it is a new installation and the installer does not replace
>existing files, there is no need to use the "Start/Stop Delayed File
>Install" feature.
>

My thinking here is predicated on my assumptions above. Two questions:

1) If my assumptions are correct, how do I conditionally switch "Start/Stop
Delayed File Install" on and off?

2) I've placed my MSDE include script very near the end of the installation
process so that other steps are performed before installing MSDE and rebooting.
Therefore, my Install File statements are divided into two places, the Install
Files script section and the MSDE include script. In this case, do I place
seperate "Start/Stop Delayed File Install" statements around each group of
Install File statements?

Greg Fasolt
G. Fasolt and Associates

www: GFasolt.com S.M.

[NewsArchive]

Hi Greg,

> I'm beginning to get a grip on this, but I believe I'm still weak on some
> basic concepts. If you can direct me to the proper topis(s) in the help
> document, that would be fine -- I just can't seem to find the answers.
>
> Additional questions within the context of your reply, below.

Okay.

> And I am grateful. SB is a great tool, a far better experience than any of
> the 3 or 4 installer tools I've used - I seem to be the weak link right
> now.

Thank you for your kind words!

>>If you have selected both the Web Installation and Web Update options in
>>your SB5 project, the compiler generates a Web Installation (instead of a
>>single-file exe) and "initializes" the Web Update technology. BTW, this
>>will *not* generate a web update!
>
> I assumed that, by configuring mt SB project in this way, that I would be
> creating the Web Installer. I also assumed that once a user installed my
> app using this installer, that I could increment the Product Version, and
> produce a new Web Installer that would automatically support the Web
> Update when the user executed wupdate.exe from the installed app. Is this
> not correct?

I would suggest not to use the same project for full installations and web
installations.

The full installation creates Add/Remove Panel entries, creates shortcuts
and registry entries, initializes the web update technology, etc.. In most
cases a web update only updates existing files.

The following is wise (IMO):

1. Create a project for your full installations.
2. Have a web update template for your web updates. You can then use
the Auto Update Generator to automatically create your web update.

We are doing the same for all SetupBuilder 5 Editions. It takes only a
few seconds to generate a web update to live update all shipped
SetupBuilder 5 versions.

>>In the above case, I would use "Start/Stop Delayed File Install" only if
>>this is an update (if you update or replace an existing application) or
>>if your web installation replaces existing files (e.g. Windows system
>>files). If it is a new installation and the installer does not replace
>>existing files, there is no need to use the "Start/Stop Delayed File
>>Install" feature.
>>
>
> My thinking here is predicated on my assumptions above. Two questions:
>
> 1) If my assumptions are correct, how do I conditionally switch
> "Start/Stop Delayed File Install" on and off?

See above. Please do not use full install and web update from the same
project base.

> 2) I've placed my MSDE include script very near the end of the
> installation process so that other steps are performed before installing
> MSDE and rebooting. Therefore, my Install File statements are divided
> into two places, the Install Files script section and the MSDE include
> script. In this case, do I place seperate "Start/Stop Delayed File
> Install" statements around each group of Install File statements?

I would create a single-file full install image. No need to use that
feature in a single-file install.

Does this help?

Friedrich

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

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

[NewsArchive]

Hi Friedrich,

Some lights are coming on!

I am now creating a template for an web updater as you suggested.

1) It seems possible a user might select the wrong Setup Type during an upgrade
and cause problems. Should I keep my Setup Types and Features or simply place
all files into Always Install? Will SB upgrade only those files already on the
target machine?

2) If I be use a different [EXENAME] for the installer, will it coexist with
the origina installer in the \Web folder? (Assuming that I adjust the
Extensions to Delete on Clean.)

3) You Wrote: "I would create a single-file full install image. No need to use that
feature in a single-file install."

I'm only using the Web Installation because of the conditional inclusion of
MSDE when a user installs my app as a demo, one of my Setup Types. Aside from
MSDE, there is little difference between my other Setup Types, so a single file
installer would be fine. Making the installer a single file to include MSDE
results in a very large file, 58MB+/-, just what I'm trying to avoid.

Does it make sense to retain the Web Installer with the full installation and
no "Start/Stop Delayed File Install" and create the web updater without MSDE
but using "Start/Stop Delayed File Install"?

Greg Fasolt
G. Fasolt and Associates

www: GFasolt.com S.M.

[NewsArchive]

Hi Greg,

> Some lights are coming on!
>
> I am now creating a template for an web updater as you suggested.
>
> 1) It seems possible a user might select the wrong Setup Type during an
> upgrade and cause problems. Should I keep my Setup Types and Features or
> simply place all files into Always Install? Will SB upgrade only those
> files already on the target machine?

Depends on your script. Please see "Replacement Options".

BTW, you have *full* control over the installation process. You can even
use If..Then..ElseIf..Else..End in your web update process.

> 2) If I be use a different [EXENAME] for the installer, will it coexist
> with the origina installer in the \Web folder? (Assuming that I adjust
> the Extensions to Delete on Clean.)

I would suggest to use different names for the full install and the web
update.

> 3) You Wrote: "I would create a single-file full install image. No need
> to use that feature in a single-file install."
>
> I'm only using the Web Installation because of the conditional inclusion
> of MSDE when a user installs my app as a demo, one of my Setup Types.
> Aside from MSDE, there is little difference between my other Setup Types,
> so a single file installer would be fine. Making the installer a single
> file to include MSDE results in a very large file, 58MB+/-, just what
> I'm trying to avoid.
>
> Does it make sense to retain the Web Installer with the full installation
> and no "Start/Stop Delayed File Install" and create the web updater
> without MSDE but using "Start/Stop Delayed File Install"?

Why not create a single-file installation and make the MSDE download
optional. Create a separate (single-file) MSDE installer. Add an option
to your main installer and offer a MSDE installer download. If user selects
this option and main installer downloaded the file, execute it and let the
MSDE installer delete itself.

What do you think?

Friedrich

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

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