Steve, one possible risk is as follows. It'll likely happen if you install any two MSIs that contain the same Component, but a different file, on one computer. The first MSI will set the Component reference. The second MSI will alter that Component reference to point to the new file. Then if you uninstall the first MSI it will probably remove the copy of the file from the second installer with it.
You can mark Components as Permanent and it might leave them alone. Since it is not a DLL I don't believe the RefCount would help at all in this situation. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Baker Sent: Wednesday, July 16, 2008 8:19 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] (no subject) Hey all, I find myself in a situation where I need some feedback on component rules. I have over 30 solutions that each have a wix installer project in them. each solution is a web site that is deployed automatically and internally. right now i have a ton of duplication between each of the install projects and am looking to reduce the maintenance overhead. i have a common wix library project that i have moved the UI and some launch conditions into. I'd like to move more into this common location but i get stuck with this particular situation. each project contains many components that look like the following: < Component Id = " StagingConfiguration " Guid = " 935B1135-E34D-49DA-843E-D984B8F2C5ED " DiskId = " 1 " > < File Id = " staging.config " Name = " web.config " Source = " $(var.Web.UI.ProjectDir)staging.web.config " /> < Condition > STAGING </ Condition > </ Component > If i moved that component (and i have at least ten more just like it) into my common wix library each web project would have the same component guid for its web.config file. I have read over the component rules again and again and can't find anything specific about doing this, but it still seems like there is something fundamentally wrong with the idea. I would appreciate if somebody could let me know what the risk is with having more than one msi contain a component with the same guid (and a different file). I have nobody here that understands windows installer to bounce the idea off. Thanks, Steve ------------------------------------------------------------------------ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
