At least one of our beta testers encountered a message that the download file was NOT a valid MSI. This was somewhat surprising as we have uploaded at least a dozen products and even more MSIs. In reviewing the Project Properties in Visual Studio prior to updating the version on the assembly I noticed that the code project (as opposed to setup project) did NOT have Enable Application Framework, Enable XP Styles and Save My.Setting checked but did have ake Single Instance checked. This was exactly opposite of all of our other projects. Offhand, while getting the choices wrong would likely cause problems at run time it did not seem that an invalid MSI should have been produced. I'd be happy to explain in excruciating detail the difference Enable app framework makes (basically, you get a console or a forms app), but the puzzle was when the MSI was built with "standard" values it installed normally. Of course, it could be that the previous version really did have some transient error like an I/O error on the disk, or that there was actually a problem not with the MSI, but with the target machine. Before torturing one or more beta testers with odd combinations of project properties I was wondering if anyone else had had this problem?
For more complete information about compiler optimizations, see our Optimization Notice.