(or shared components) in a separate msi
that doesn't get uninstalled automatically on product2 removal.
Or some horrendous custom action that puts the dependent dll back if you are
removing it and will break product1.
Dave
-Original Message-
From: Michael Partridge [mailto:michael.partri
This might be a silly response, and I haven't had to think about Property
behaviour for a while, but isn't that the wrong way to set a Property to the
value of another Property? From http://msdn.microsoft.com/library/aa370908.aspx
it says:
Note that you cannot use the Property table to set a
: 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
, 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
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-component
was discussed?
Basically, I have Product1 (already released) and Product2 (in development)
which both share the same component A.dll. A.dll is
5 matches
Mail list logo
