We are having a problem where there is interaction between two different install packages that should be independent. What we see is that if both are installed, uninstalling either one of them won't remove all files/registry keys/shortcuts. For example, if I call the two packages “#1” and “#2”: Install #1, then install #2, then uninstall #1 - it leaves behind some of #1’s files. Similarly, if you install #1, then install #2, then uninstall #2 - it leaves behind some of #2’s files. However if only one or the other was installed, both work just fine, removing everything.
Note that we created package #2 by starting with a copy of #1. But we have changed the package GUID, product GUID, and version GUID on #2. It seems like if all 3 of those things are changed, then the two packages should be completely independent. But apparently they are somehow still linked. Is there anything else we need to make sure is different between the two packages to make them truly act independently?
Are the files in the two packages the same? More specifically, are any of the component GUIDs in the two packages the same? What you describe sounds like the behavior when two products share common components.
KathyMorey wrote: Are the files in the two packages the same? More specifically, are any of the component GUIDs in the two packages the same? What you describe sounds like the behavior when two products share common components.
Thanks, Kathy. Changing the component GUIDs fixed the problem. 🙂
