Donal McWeeney wrote: > Thanks for the answer. After understanding the upgrade table a bit more > I realised that the previously authored msis were installed per-user and > we need to do it per-machine, and the FindRelatedProducts does not > search across context. >
It doesn't do that because it's frequently not possible. For example, even an admin user wouldn't be able to peek into the per-user registry of a user whose profile isn't loaded (e.g., roaming profiles). I'd suggest another approach, like using RegistrySearch or FileSearch to look in well-known locations. (That assumes you didn't have the previous install going into per-user directories like LocalAppData.) Then if FindRelatedProducts doesn't find anything, you can throw up a dialog telling the user to uninstall manually. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
