Once you have built a complete installer package (.msi) file, you might want to run it to test your product installation.
You must be aware of an important Microsoft® Windows® installer consideration whenever you run a changed version of an installer package (.msi) file. This is that the installer, after successfully installing an application, maintains a cached version of the original .msi file on the target machine. This cached copy of the .msi file is an important safeguard for your user, because it maintains the information necessary for any future installation repairs.
However, this cached version of the .msi file can interfere with testing and debugging, because the Windows installer will always run the cached .msi file, unless it is uninstalled. That means, you could make changes to a Microsoft® Visual Studio® Installer project (.wip file), build them into a new version of your installer package (.msi) file, and then run the installer package — and the new installation will not include any of your changes. That's because the Windows installer would run the original, cached version of the .msi file not the newer version you have just built.
To ensure your changes are incorporated into the product installation, you must uninstall any older version of the .msi file before you run the newer version. To accomplish this, you can either:
–or–
To run an installer package file from inside the Microsoft development environment
Before starting this procedure, make sure you have built the installer project (.wip) file into an installer package (.msi) file.
Visual Studio Installer will uninstall any cached version of this .msi file that exists and then launch the updated installer.
To run an installer package file from Windows Explorer
Before starting this procedure, make sure you have built the installer project (.wip) file into an installer package (.msi) file.
–or–