No. Let me see if I can explain a little better. I have MSI called MSI_A that installs ComponentX with GUID 1111 (example) and MSI_B that also installs ComponentX with GUID 1111. ComponentX installs Website "NEWWebSite". Both installs will configure the site Exactly the same. If I were to uninstall either MSI_A OR MSI_B, the site gets removed. I would assume since component rules are such that if more than one installation uses a component with the same GUID, that the uninstall won't remove it. This doesn't seem to be the case with the IIS WiX section.
-----Original Message----- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Tuesday, February 08, 2011 9:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] IIS Sites and Component Rules To be clear, do you have multiple Components in the same MSI with the same Component/@Guid? If so, then that sounds bad and I don't know what behavior the Windows Installer would have (but it won't be defined). On Tue, Feb 8, 2011 at 11:13 AM, Pierson Lee (PIE) < pierson....@microsoft.com> wrote: > I have an application that contains 5 components. Each component > installs a Virtual Directory onto a website and each MSI has the > website component to install if it doesn't exist. These website components > all share a GUID. > > My problem is that on uninstall, it doesn't seem to check that there > are other applications that are using the component and it uninstalls the > site. > I would assume that since 5 components have the same component and > component GUID, that it would go by the counter system where the > component wouldn't uninstall until no other installations are using > it. Is that not the case with the IIS components? > > Using Wix 3.0RTM and wix 3.5.2519.0 > > Thanks > Pierson > > ---------------------------------------------------------------------- > -------- The ultimate all-in-one performance toolkit: Intel(R) > Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
