The Windows Installer is an operating system service that was developed by Microsoft to improve the installation and uninstallation of programs, make software deployment in corporate networks easier, and to solve common problems such as shared dll conflicts. The Windows Installer is also a set of rules that developers must follow to take advantage of the service. To use all the features, your application has to be "Windows Installer aware" - so you have to think about installation already when you plan and write your application, not after everything is complete. For example you need to call a special API to enable just-in-time installation of parts of your application (see below).
The Windows Installer has formerly been called "Microsoft Installer" (MSI). Therefore the names of the API functions start with "Msi", and the installer packages have the .MSI extension.
Books, Articles and Specifications
The installer registers the application, creates shortcuts and menu entries, associates file types etc. without actually copying the application files to the user's hard drive. If the user or another application tries to access the advertised program, it is installed on demand. In this case the invoking of the installer is handled by the operating system.
This is quite similar to Advertising. However it doesn't refer to a whole application, but to a feature or function that is called from inside the application (e.g. an import filter). When the application tries to access the feature and finds that it isn't present, it calls the installer service to install it just in time. This way users don't have to anticipate the functionality they need before they ever used the product. Requirement: The application must be modified to call the Windows Installer API.
When launching an application, files, registry entries etc. are automatically checked. If they are deleted or damaged, the component is installed again.
Setup can run with Administartor privileges even if it is launched from a normal user account.
The installer records all changes it makes to the system, and creates temporary backup copies of overwritten files. If setup is aborted, the system is reverted to its previous state. After the setup is finished successfully, the rollback information and backup files are deleted to save disk space. (Do not confuse this with uninstallation).
You can deliver run-time components (e.g. VB Runtime) or operating system updates by importing a merge module (.msm file) into your installer package. This avoids the problems with having to launch external third party setups or mimic their behaviour.
Windows 2000 and Windows 98 Second Edition introduce another measure to avoid version conflicts with shared DLLs (aka "DLL Hell"). It is now possible to load several versions of the same file into memory. Microsoft recommends that files like COM servers are no longer copied to a common location but to the application directory. This requires modification of the application to enable it to load components from the application directory, and modifications to the component to avoid conflicts with other instances of the same file. And of course such a component must be registered in a special way, which can be done with the Windows Installer. This also avoids the need for a reboot, because a component located in the application directory will not be in use (locked) by a different application.
Microsoft White Paper about Side-by-Side Sharing of Components
Transforms can be used to customize installation, e.g. to deploy different configurations of an application to different departments in a company, to localize a product, or to apply upgrades. The Transform does not change the actual installer package. Instead the installer database is loaded into memory, then the transform is applied to this database and finally the installation takes place.
Windows Installer supports several ways to update an existing package. Basically, these are Transforms, but they can be delivered as binary patches.
|News||Discussions||Windows Installer||Virtualization||Related Tools||More Help||InstallScript||About InstallSite||Shop||Site Search|
|Neuigkeiten||Diskussionsgruppen||Windows Installer||MSI FAQ||Artikel||Shop||Suche|
Copyright © 1997-2013 by InstallSite Stefan
Krueger. All rights reserved. Legal
By using this site you agree to the license agreement. Webmaster contact