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-componentwas
>  discussed?
>
> 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/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



------------------------------------------------------------------------------
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

Reply via email to