At last you are ready to submit your application. You have created your MSI installer, and you are reviewing the Packaging Requirements document to ensure your hard work will pass validation right away. As you are reading you see "Silent Install..", and either wonder what this requirement means or think you have it covered. Read on as I explain this requirement and how to address it in a Visual Studio 2008 Package and Deployment project.

Why do we have this requirement?

The Intel AppUp center has provided (Formerly referred to as the App Store), functions as an interface for end users to download our apps. As such it also has the duty of launching our MSI installers once the user has download our application. A seamless flow from searching, downloading all the way to running your application is expected by the user. The UI through this process remains consistent in both style and functionality. The reasons for a silent install requirement include:

1.) A consistent user experience. Users are presented with the same installation experience whether they are installing a game from XYZ company or a utility from 123 Corp.

2.) Tight integration with the Intel AppUp center. The MSI standard allows for parameters including installation path, culture and more. The Intel AppUP center handles these things for us, and removes the burden of clicking through the installer wizard for the user.

How can I test my MSI to determine if it will pass this validation requirement?

This is quite simple. Execute your MSI, then answer this question.

"Was I required to click anything during the installation process?"

If you answered NO, congratulations your MSI will pass this requirement. However, if you answered YES then you may want to read on for a relatively easy fix.

* The following screen shot depicts an MSI which would pass this validation requirement. Note that no user input is required for the validation to complete.

How do I implement this "Silent Installation" in Visual Studio?

Fortunately this is quite simple and should not cause most installers implementation problems (See below if you find yourself in this situation)

1.) Open your Visual Studio Package and Deployment project.

2.) Right click on your project in the Solution Explorer and select View -> User Interface

3.) Remove all dialogues

4.) Recompile and test for validation compliance (* See above)

Implementation Problems

Some MSI installers prompt for additional information from the user during the installation process. This will cause validation to fail. What can be done? Simply move this data collection logic into your program so that it is executed the first time your app is ran. Although slightly inconvenient, it is a viable solution adopted by several ATOM developers to date.

Additional resources
HOW TO: Create an MSI installer using Visual Studio 2008

Should you run into any problems please visit the Forums for assistance. Best of luck!