Preparing to install...
Hello,
I have used external UI (using SetExternalUI function) for my installation. Since the application contains huge number of files, it spends considerable amount of time on "Preparing to install..." screen (I tested it by simply using .MSI) and thus there is no progress on custom UI.
Is there any way I can reduce this time????
I have used external UI (using SetExternalUI function) for my installation. Since the application contains huge number of files, it spends considerable amount of time on "Preparing to install..." screen (I tested it by simply using .MSI) and thus there is no progress on custom UI.
Is there any way I can reduce this time????
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
AngelD
13 years ago
check that not each file is located in its own component, remember; one executable per component.
Depending on the Windows Installer version that is going to be targeted you could use the MSIFASTINSTALL property
Depending on the Windows Installer version that is going to be targeted you could use the MSIFASTINSTALL property
Posted by:
milindsm
13 years ago
check that not each file is located in its own component, remember; one executable per component.
What do you mean by that??? Didn't get you :(
Posted by:
pjgeutjens
13 years ago
Milind,
does a verbose log tell you anything about which actions are taking a long time? I don't know by heart which actions are executed in an msi sequence while the "preparing to install" message shows, but I would guess it's a number of costing actions (seeing how much resources the installer will need). Maybe some action is messing around with the source files...
What Kim meant about the components, is that if you have 10.000 text files you can put them all in 1 component instaid of 10.000 components, as long as there are not more than one exe/dll/ocx in 1 component. This might save Windows Installer some time.
Anyway, just check the logs and go from there.
PJ
does a verbose log tell you anything about which actions are taking a long time? I don't know by heart which actions are executed in an msi sequence while the "preparing to install" message shows, but I would guess it's a number of costing actions (seeing how much resources the installer will need). Maybe some action is messing around with the source files...
What Kim meant about the components, is that if you have 10.000 text files you can put them all in 1 component instaid of 10.000 components, as long as there are not more than one exe/dll/ocx in 1 component. This might save Windows Installer some time.
Anyway, just check the logs and go from there.
PJ
Posted by:
milindsm
13 years ago
How can I use single component for multiple files.... its a primary key..... (I hope I am not interpreting your answer incorrectly!!!)
Posted by:
anonymous_9363
13 years ago
Some good reading here on the subject.
(How boring is Saturday night TV in the UK? Why else would I be here?)
(How boring is Saturday night TV in the UK? Why else would I be here?)
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.