A corrupt file will not trigger Windows Installer to perform a self-repair. This is because the Windows Installer checks only for file existence when checking a component that uses a file for its keypath. Read on to learn more.
With Microsoft Windows Installer, an application's entry points play a major role in installing advertised features and initiating the self repair of an application. When a user uses an entry point to launch an .MSI-based application, Windows Installer performs an integrity check by verifying:
Here are a couple of approaches that'll keep that pesky Windows Installer away from files you don't want uninstalled when an uninstall script is run. Hope you find this info useful.
Bootstrapping is nothing but a process. Until the Windows Installer Service is pervasive, any software that depends on the Windows Installer being present must first ensure that the Installer is in fact present.
A Windows Installer Transform (.mst) contains a set of alterations to a Windows installer package (.msi). In order to correctly view the changes a transform makes, the .msi package that served as the 'original' should be used as the base package. Read on to learn what the MST viewer is and how to get some mileage out of it.
DirectX has been included on several different releases of programs, drivers, and games. I'm always looking for a definitive list of versions numbers. Below is a listing of each of the DirectX versions and their associated versions.
Uninstallation for the Installshield applications sometimes use rundll32.exe. Here are some of the different silent uninstallation cmd lines that I've come across:
The latest Adobe Suite applications come with install.xml and uninstall.xml files. You can edit the XML and decide which application you need to install from the suite of apps. Here's some info about doing just that.
We Can set the following property values as an administrator option in Wise Package studio instead of giving the values in the properties. This option is not used by most package developers.