This site uses cookies to offer you a better browsing experience. Find out more on how we use cookies and how you can opt out. Accept
PACE Suite - Application Packaging & Virtualization Software
Request a trial Get a quote Become a partner
Request a demo of PACE Suite now We will get in touch with you right away to schedule a convenient time for your 1-on-1 demo with one of our experts.
I have read and agree to the Privacy Policy
Request a quote Please fill in this quick form and we will send you a free quote shortly.
License *
 Freelancer Enterprise Service Provider
I have read and agree to the Privacy Policy
Request a quote Please fill in this quick form and we will send you a free quote shortly.
License *
 Freelancer Enterprise Service Provider
I have read and agree to the Privacy Policy
Request a call Please fill in this quick form and we will call you back shortly.
I have read and agree to the Privacy Policy
Contact Support Please fill in this quick form to contact our support.
I have read and agree to the Privacy Policy
Subscribe to our Newsletter Be among the first to receive our updates! Fill in this quick form to join the list of subscribers.
Send an email to Tetiana Botanevych Please fill in this quick form to contact our expert directly.
I have read and agree to the Privacy Policy

MSI Package Complexity Estimation (+ more useful reports)

The importance of proper documentation in application packaging is indisputable. As packages go through increasingly more modifications and grow more complex over the years, it is important to know the current state of a package at any time. That is why PACE Suite offers automatic package complexity estimation and a number of reports to go with it.

MSI Package Complexity Estimation

To get an automatic complexity estimation of your MSI package, you need to open your MSI with MSI Editor, a part of PACE Suite. Once MSI Editor opens, you will see the Application tab.

open package in msi editor

Here, apart from the standard application details and summary information, you can also find MSI package complexity estimation.

msi complexity estimation in msi editor

It calculates numbers of resources in you package and displays one of the complexity levels. PACE Suite has 4 complexity levels: basic, easy, medium and complex. The complexity estimation criteria are saved in an XML file and can be changed according to your needs. As your work with your package in MSI Editor and gradually make it more complex (or easier), the complexity estimation results will be updated in real time – just click Refresh.

You can export complexity estimation results into Excel spreadsheet by clicking Export results. Save your report and open it.

msi package complexity estimation report

In your report, you can find the general information about the package – manufacturer, product name, and version. Automatic estimation displays the number of automatically calculated resources (e.g. the number of scripts present in your installer), package size and complexity level.

Note the criteria No 19 “Number of ICE errors in existing package to be checked/fixed”. If you run MSI package validation to find errors, your complexity estimation will be updated automatically, and you will also see their number when you genreate a report afterwards.

The manual estimation section allows to select additional criteria and calculate the complexity level more precisely.

MSI Package Report

You can also generate a package report using MSI Editor. Go to MENU and then click Generate package report.

creating msi package report

In the opened window, select a template. MSI Editor offers two default templates but you can modify them according to you needs (you can click “How to create a new template” link to find instructions on how to edit them). Once you are done with choosing templates, click Generate and then save you report.

msi package report

Package report includes basic information about your package such as its size, INSTALLDIR, package GUID, default deployment commands, and information about package resources like services, properties and so on.

Depending on your business needs, you may use these reports as components of your package documentation or simply when you need to get a quick understanding of the package you are about to edit. Either way, both reports should come in handy for any packager.

Share this blog article: