Handling of Installation of External Components

[John1969john]

Hi,

We are currently using a different installation builder with which we have run in to some problems re. the installation of MDAC and the .NET Framework.

Now I have downloaded Setup Factory 7.0 (Trial) and I have seen that there are special facilities to deal with the installation of MDAC and .NET.

I have seen that the setup program performs Technology Updates, this all works fine on our development PC's and 'Clean' PC's that have been kept up to date and represent te state that we would expect a normal working PC to be in.

As you all know: There are many many many exceptions out there, PC's that have limited access, PC's that use Installation servers, Citrix, not updated machines, partially updated machines, other software (like MS Office) that reconfigures itself after updates of MDAC and so on.

My questions are:

1. What happens when the Technology update fails (for instance due to inaddequate rights)? - Does the installation abort - Is there a way to inform the customer re. possible remedies/ detailed status ?

2. Does the system handle failure of the installation of Components like dotnetfx.exe (lets say .NET fails to install due to a malfunctioning component of a previous installation) and is there a way to inform the customer re. possible remedies/ detailed status ?

3. Is there a way to download and install dotnetfx.exe and mdac_typ.exe externally if needed by the targetPC? - This helps to slim down the initial installation set?

Thanks in advance,

John

[Eagle]

Hi there..

Generally speaking to answer 1. and 2.

you will find that making use of the 'Dependancy Module' handling
in Setup Factory 7 is very powerfull and the dependancy modules
available for use have error handling -install conditions-version
checking and Account Permissions handling etc builtin.
You can modify these downloadable modules to suit your specific needs..thats the beauty of them.

for 3. the dependancy modules currently are coded (instructions
and direct download links are provided to you ) to have the
dependancy exe's available and access is coded into the Modules.

you could however code in to instruct user to download XYZ etc.
and then advice user to implement or offer to Install via Code.

If you want 'control as to success for the User, its only a suggestion,
however I would probably go for including the Exe's in your 'package'
and live with the 'install overhead' ..just my 2 cents on that.

User information notices are coded into the downloadable modules.
..as mentioned you can customise anything you like.

http://www.indigorose.com/forums/forumdisplay.php?f=44

how to use is provided with each Module at above link
you can 'chain as many modules in one Setup Package as you need.

HTH

[John1969john]

I see,

Cheers,

John