This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: BASIC MSI: Question about install time
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 04, 2014
11:19 AM
BASIC MSI: Question about install time
I have a question about an installation package that I am working on.
I have 'mirrored' the package from an older wise installer package that is currently being delivered to our customers. It includes about 7 COM assemblies. In the Wise installation package, the COM files are registered by means of a series of batch files that are executed at the end the install and the entire process takes roughly about 2 minutes using regasm to register the COM files and create the new /tbl files.
However with the InstallShield package, I want to do the right thing and create a better install. So I included the COM assemblies in the MSI package for registration instead of using the batch files.
What we are seeing in testing however, is that the process of writing to the registry increases dramatically. The wise installer product from the same build machine takes about 11 minutes to install with all of the prerequisites. My new InstallShield package is taking just over 40 minutes to complete the same configuration on the same test environment.
Looking at the log file just writing to the registry takes almost 18 minutes of a 21 minute install process. So if the log file is to believed, it took only 3 minutes to transfer files to the system and 18 minutes to write all the registry entries! It is difficult for me to justify to managers the advantages of MSI and COM registration with numbers like this.
So is this normal?
COM seems to have been installed properly. The application behaves properly without any errors and uninstall works correctly, all references to the assemblies are removed from the registry.
Unfortunately I am not an expert at COM so I am not sure what to expect here. Hopefully someone with more experience in this domain can shed some light on this.
Thank you so much.
Also, I am unable to explain why other prerequisites are taking longer to install. For instance. My suite package includes SAP Crystal Reports 13.1 and the Wise Installer includes it as well. It takes almost 7 minutes to install using InstallShield but only about 3 minutes using Wise Installer. I cannot explain the discrepancy because I am using the very same redistributable and I cannot see where the wrapping app would have an affect on the time it takes to deliver the package from the time it launches to the time it finishes.
I have 'mirrored' the package from an older wise installer package that is currently being delivered to our customers. It includes about 7 COM assemblies. In the Wise installation package, the COM files are registered by means of a series of batch files that are executed at the end the install and the entire process takes roughly about 2 minutes using regasm to register the COM files and create the new /tbl files.
However with the InstallShield package, I want to do the right thing and create a better install. So I included the COM assemblies in the MSI package for registration instead of using the batch files.
What we are seeing in testing however, is that the process of writing to the registry increases dramatically. The wise installer product from the same build machine takes about 11 minutes to install with all of the prerequisites. My new InstallShield package is taking just over 40 minutes to complete the same configuration on the same test environment.
Looking at the log file just writing to the registry takes almost 18 minutes of a 21 minute install process. So if the log file is to believed, it took only 3 minutes to transfer files to the system and 18 minutes to write all the registry entries! It is difficult for me to justify to managers the advantages of MSI and COM registration with numbers like this.
So is this normal?
COM seems to have been installed properly. The application behaves properly without any errors and uninstall works correctly, all references to the assemblies are removed from the registry.
Unfortunately I am not an expert at COM so I am not sure what to expect here. Hopefully someone with more experience in this domain can shed some light on this.
Thank you so much.
Also, I am unable to explain why other prerequisites are taking longer to install. For instance. My suite package includes SAP Crystal Reports 13.1 and the Wise Installer includes it as well. It takes almost 7 minutes to install using InstallShield but only about 3 minutes using Wise Installer. I cannot explain the discrepancy because I am using the very same redistributable and I cannot see where the wrapping app would have an affect on the time it takes to deliver the package from the time it launches to the time it finishes.
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 06, 2014
05:55 AM
My MSI is bundled within a suite package. There is an option for the level of logging, from actions to 'actions and action data'. I had the later selected for debugging the installation process initially. What I did not know was that it would add so much time to the install process.
Changing it back to just 'Actions' changes the install time of over 20 minutes to just 8min 45sec.
Changing it back to just 'Actions' changes the install time of over 20 minutes to just 8min 45sec.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 06, 2014
01:48 PM
Hey Dan,
Where is that setting? The only one I see is Yes/No at the Package level of the Suite.
Thanks
Where is that setting? The only one I see is Yes/No at the Package level of the Suite.
Thanks
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 06, 2014
03:06 PM
The option is 'Status Messages Reported'. Make sure it is only set to 'Action Text'.
If you do a compare of your XML changes after you will notice that the setting changed from FullVerbose to Full.
If you do a compare of your XML changes after you will notice that the setting changed from FullVerbose to Full.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 06, 2014
04:25 PM
Great!
Thanks Dan
Thanks Dan