If you want the Windows Logo on your product, you are going to have to know how to validate a release image. Even if you aren’t going for the Windows Logo, validating your releases is still a good idea.
I have noticed there is one problem people have the first time they try to do this is. Take a look at the screenshot below.
Here, you are in the Releases view for a Basic MSI project, and you are trying to validate a Single Exe release, but when you go to the Build, Validate menu, all of the selections are disabled.
The reason is simple. Take a look at the release folder for the Single Exe release.
The only file in the release is Setup.exe (I’ve renamed the file in my example, but you get the idea), where all installation files are compressed into a Single Exe file. And that is the problem.
To validate a release, InstallShield must have access to the MSI database file.
Here is the release folder for a CD-ROM release.
In contrast, there are several files, one being the MSI database file. Because of that, you will have no problems validating this release. Selecting the CD-ROM release, here is what you see when you go to the Build, Validate menu.
All of the validatation suites are enabled and ready to use.
Remember this when you are having problems validating your release.