---- Blair <os...@live.com> wrote: > (keeping the thread on the list so future generations can benefit) > > The source list is described here: > http://msdn.microsoft.com/library/aa369795.aspx and here: > http://msdn.microsoft.com/library/aa371859.aspx along with a few other > places. It is the list of directories that Windows Installer will search to > find the non-stripped version of the MSI for each installed product whenever > it needs it (you get a ResolveSource prompt when that search fails). The list > contains just the directories: the MSI's name is separately stored and can't > be changed. When a product is uninstalled, the associated source list is > automatically removed (along with all other metadata related to that > product). The content of that source list, however, is not (so you would need > to remove your cached MSI when your product is removed).
I see. So as I understand it, I have to keep the MSI around while the software is installed. Is there a recommended location for such cached MSIs? And is it even possible for the MSI to delete itself during uninstall? How does Burn handle this? > A component is Windows Installer's atomic unit of installation: it consists > of resource(s) (files, registry values, etc.) that assume one identity (the > keypath of the component) and one name (a GUID for cross-package use and an > identifier for use within a given database) and the identity is used to > determine the entire component's "health" and status: for that reason it is > generally encouraged that you have only one file per component. Search for > "Component Rules" to get a feeling for what you "need to know" to avoid > creating packages that can't be upgraded/serviced/cleanly removed. > > A feature is the fundamental user selection "grouping" of what is or isn't > installed (in MSWord, for instance, a spell-check for any arbitrary language > dictionary is a feature, as the program can run with or without it). That > appears analogous to your use of the term "component" in your first email in > this thread. > > A product is a collection of features and components (any given component may > be a member of more than one feature but must be a member of at least one or > it could never be installed, removed, or even maintained) that can exist > independently of any other product, is instanced such that only one can be on > any given computer at a time. Products can be tied together in a family via > an UpgradeCode which is typically used to remove old versions and prevent > downgrading (overwriting a newer version by replacing it with an older one). > Products are supplied via a package (an MSI database file) which provides the > complete definition of an arbitrary instance of a product. > > MSI can copy or move files (which includes renames) but typically it moves > them after overwriting them. You can extend MSI via custom actions which you > can use to rename your .ini files. WiX provides for the use of just about > every feature available in Windows Installer (in fact, if one were so > inclined, you could reauthor every other MSI file in WiX). Thanks, that was very detailed and clear explanation. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
