This is now a bug in product1. It needs fixing at a priority that your product owner decides. You must have an update strategy for that product, what if it has a critical security issue/flaw?
You could release product2 as a burn bundle and include a fix in it for product1 by adding a major upgrade msi or msp to it along with your product2 msi. Dave -----Original Message----- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 13 August 2013 15:16 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Adding a new dependent file to shared component without breaking component rules No, don't force features to not be uninstalled when uninstalling. Crazy things will happen. In general, don't mess with feature selection lightly. Michael, I misread the word "dependency". I think you have analyzed the math on this correctly. This is one of the scenarios where the Component Rules are fundamentally broken. Windows Installer expected you to not add dependencies like this... but devs will be devs and it'd be nice if they actually handled it correctly. On Tue, Aug 13, 2013 at 2:55 AM, Blair Murri <os...@live.com> wrote: > You could put D2.dll into its own feature, and force that feature to > not be removed on product removal if product 1 is still installed. You > get the same "effect" of D2.dll getting orphaned but at least you > don't perpetrate the problems of sharing binaries in the same > component in all other scenarios. > > > From: michael.partri...@petrosys.com.au > > To: wix-users@lists.sourceforge.net > > Date: Tue, 13 Aug 2013 04:07:56 +0000 > > Subject: Re: [WiX-users] Adding a new dependent file to shared > > component > without breaking component rules > > > > If I put D2.dll in its own component, then, assuming Product1 and > Product2 installed, when Product2 is uninstalled, D2.dll will be removed. > However, A.dll will still be at version 1.1.0, so will have lost its > dependency and thusly won't run. > > > > NB: I can't change Product1 - it's already in the field and won't > > have > any updates. In reality Product1 and Product2 are different versions > of our product that can be installed side-by-side - users like to have > access to previous versions. > > > > Cheers, > > Michael > > > > -----Original Message----- > > From: Rob Mensching [mailto:r...@robmensching.com] > > Sent: Monday, 12 August 2013 6:14 PM > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Adding a new dependent file to shared > > component > without breaking component rules > > > > Why not put D2.dll in it's own Component? > > > > > > On Sun, Aug 11, 2013 at 10:37 PM, Michael Partridge < > michael.partri...@petrosys.com.au> wrote: > > > > > Hi All, > > > > > > I was wondering if the state of play has changed at all since > > > > http://stackoverflow.com/questions/703359/wix-add-new-file-to-shared-componen twasdiscussed? > > > > > > Basically, I have Product1 (already released) and Product2 (in > > > development) which both share the same component A.dll. A.dll is > > > installed to %COMMONFILES%/MyProducts/. > > > > > > Product1 installs A.dll version 1.0.0, which is dependent upon D1.dll. > > > Product2 installs A.dll version 1.1.0, which is dependent upon > > > D1.dll and D2.dll. > > > > > > Due to the way that A.dll is used (it's a COM component registered > > > in a thirdparty application, and we can only register one .dll) > > > there isn't the option of creating newA.dll and putting that into Product2. > > > (At least not without breaking Product1.) > > > > > > I think my only option is to add D2.dll in A.dll's component, > > > breaking the component rules, and live with the fact that D2.dll > > > will remain on the user's computer if they uninstall Product2 then > > > uninstall Product1. At least then, if someone uninstalls Product2 > > > our .dll will continue to run correctly. > > > > > > Does anyone have any further insight? > > > > > > Thanks, > > > Michael > > > > > > ------------------------------------------------------------------ > > > ---- > > > -------- Get 100% visibility into Java/.NET code with AppDynamics > > > Lite! > > > It's a free troubleshooting tool designed for production. > > > Get down to code-level detail for bottlenecks, with <2% overhead. > > > Download for free and get started troubleshooting in minutes. > > > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/os > > > tg.c lktrk _______________________________________________ > > > WiX-users mailing list > > > WiX-users@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > > > ---------------------------------------------------------------------- > -------- > > Get 100% visibility into Java/.NET code with AppDynamics Lite! > > It's a free troubleshooting tool designed for production. > > Get down to code-level detail for bottlenecks, with <2% overhead. > > Download for free and get started troubleshooting in minutes. > > > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.c > lktrk > > _______________________________________________ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > > > ---------------------------------------------------------------------- > -------- > > Get 100% visibility into Java/.NET code with AppDynamics Lite! > > It's a free troubleshooting tool designed for production. > > Get down to code-level detail for bottlenecks, with <2% overhead. > > Download for free and get started troubleshooting in minutes. > > > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.c > lktrk > > _______________________________________________ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ---------------------------------------------------------------------- > -------- Get 100% visibility into Java/.NET code with AppDynamics > Lite! > It's a free troubleshooting tool designed for production. > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.c > lktrk _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ----------------------------------------------------------------------------- - Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
