[wix-users] IGNOREDEPENDENCIES property?

[Reuss, Matthias]

Hi Phill,

Thank you for the explanation.

If I understand you correctly, this property is read and used by some custom action which comes with the WiXDependencyExtension. So I assume it is ignored if I do not use this Extension in my MSI, isn't it? In WiX 3.9, Burn does such a cross-bundle dependency handling even without referring to the WiXDependencyExtension in the bundle.

Anyway, if the MsiPackage which is being uninstalled has not built with WiX, I assume that IGNOREDEPENDENCIES is ignored at all, isn't it?

Best regards

Matthias Reuss

-----Ursprüngliche Nachricht-----
Von: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] Im Auftrag von Phill Hogland
Gesendet: Freitag, 13. November 2015 20:19
An: WiX Toolset Users Mailing List
Betreff: Re: [wix-users] IGNOREDEPENDENCIES property?

>> What is the purpose and meaning of the IGNOREDEPENDENCIES msi property, which is e.g. set if I uninstall an MSI package from a bundle? I cannot find that property in Windows Installer documentation.
It is documented in the Wix Toolset source code as Burn functionality, related to the WixDependencyExtension.  It appears to be a way of specifying in an MSI a delimited list of specific XxxPackages, which is also in the bundle's chain, which should not be treated as a dependency of the particular MSI which has the property defined (with the list of package IDs or with  "ALL").  I don't have any experience using this feature, but that is my understanding from briefly looking at the code.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Wesley Manning
Sent: Friday, November 13, 2015 1:08 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] IGNOREDEPENDENCIES property?

Two different MSIs could install the same components with the same GUID and install location and that means component counting is in effect.  Wouldn't component counting (forget exact term, reference counting maybe) handle this as well?  IGNOREDEPENDENCIES I guess is useful for non-MSI installers or when you didn't plan ahead?

Wes

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Carter Young
Sent: November-13-15 2:28 PM
To: wix-users at lists.wixtoolset.org
Subject: Re: [wix-users] IGNOREDEPENDENCIES property?

Simple Component Rules enforce MSI behavior and are used for checking.
Continuing with my example:

Component Rule in Game Whizzbang checks that .NET 4.5.2 is installed. 
It was installed via the Component Rule in Software Suite A.  The MSI tables are only built on a per MSI basis.  There is no way that Software Suite A knows that Game Whizzbang requires .NET(2 Different MSI's have 2 Different Scopes, that isn't Global).  That's what IGNOREDEPENDENCIES is for.  The only person who knows they are both installed is you, and your Programs and Features.

Carter

On 11/13/2015 12:37 AM, Reuss, Matthias wrote:
> Thank you for the input.
>
> So in which Windows Installer version was IGNOREDEPENDENCIES introduced? I wonder why I do not find documentation.
>
> Moreover: Shouldn't simple component rules enforces the behaviour that you just described below?
>
> Best regards
>
> Matthias
>
> -----Ursprüngliche Nachricht-----
> Von: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] Im 
> Auftrag von Carter Young
> Gesendet: Freitag, 13. November 2015 03:39
> An: wix-users at lists.wixtoolset.org
> Betreff: Re: [wix-users] IGNOREDEPENDENCIES property?
>
> IIRC:
>
> Consider the following:
>
>  1. You install Software Suite A.
>  2. Software Suite A Contains Executable B, and DLL C.
>  3. At Install Time B and C are dependencies of A.
>  4. You also built Software Suite D, which also uses B and C.
>
> Ignore Dependencies allows me to uninstall A while leaving B and C on 
> the system so that D Continues to Function. This is most commonly used 
> with .NET Framework Versions.  If Suite A requires version 4.5.2 and 
> it isn't installed your installer should install it as a dependency.
> In the meantime, I downloaded Game Whizzbang that also requires 4.5.2.  
> If I unistall Suite A and include the dependency in the Uninstall, 
> I'll unintentionally break Game Whizzbang
>
> Carter
>
> On 11/12/2015 08:40 AM, Reuss, Matthias wrote:
>> Hello,
>>
>> What is the purpose and meaning of the IGNOREDEPENDENCIES msi property, which is e.g. set if I uninstall an MSI package from a bundle? I cannot find that property in Windows Installer documentation.
>>
>> Best regards
>>
>> Matthias Reuss
>>
>> ____________________________________________________________________
>> WiX Toolset Users Mailing List provided by FireGiant 
>> http://www.firegiant.com/
>>
>>
>>
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant 
> http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant 
> http://www.firegiant.com/
>
>
>



____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/