[WiX-users] Difxapp Component Installation condition

[Marc Beaudry]

Hello All,

I am using Difxapp for the first time, my installation is successful as long
as the hardware I am installing it present in the system.

I searched and can't find an answer to my question, maybe my key words are
incorrect. Please let me know if this is possible.

The MSI I have installs a driver and other applications. Because of
different possibilities, the hardware may in some cases not be present in
the system. When this is the case my MSI fails the installation and Rolls
back.

Is it possible to ignore the success state of a specific component (in this
case the one responsible for installing the device drive) to allow the
installation to be successful regardless of whether the hardware is present
in the system or not?

Here is the solution I have in mind: Write a CA to scan the system for the
device and attach this to a property and install the component based on the
property's value. Is there a better way?

Thanks for the advice,
Marc



------------------------------------------------------------------------------

[Phill Hogland]

I use the WixDifxAppExtension to install multiple drivers in configurations
where in most cases the hardware will not exist, because they are different
types of printer drivers and no hardware, or one model of printer is
expected. Maybe the difference is related to the DifxApp flags. In my
Component which includes the INF file as the keypath, I also have:
<difx:Driver AddRemovePrograms="no" PlugAndPlayPrompt="no" />



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Difxapp-Component-Installation-condition-tp7600921p7600924.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------

[Marc Beaudry]

Thanks for the response, the issue was in my KeyPath file set. I had put my
'MainDrv64.sys' file as the key path in the component, changing it to the
INF allowed the installation to go through even though the hardware is not
present.

Here is my full component in case anyone has the same issue.

<Component Id='MainDrv64' Guid='f02c999a-8699-4499-9d99-999999999999'
Win64="yes">
<File Id='MainDrv64.sys' Name='MainDrv64.sys' DiskId='1'
Source='MainDrv64.sys' KeyPath='no' />
<File Id='OtherDrv64.sys' Name='OtherDrv64.sys' DiskId='1'
Source='OtherDrv64.sys' KeyPath='no' />
<File Id='MainDrv64.inf' Name='MainDrv64.inf' DiskId='1'
Source='MainDrv64.inf' KeyPath='yes'/>
<File Id='MainDrv64.cat' Name='MainDrv64.cat' DiskId='1'
Source='MainDrv64.cat' KeyPath='no'/>
<difx:Driver AddRemovePrograms="no" Legacy="yes" PlugAndPlayPrompt="no"
Sequence='1' />
</Component>

-----Original Message-----
From: Phill Hogland [mailto:***@rimage.com]
Sent: July-22-2015 12:59 PM
To: wix-***@lists.sourceforge.net
Subject: Re: [wix-users] (deprecated) Difxapp Component Installation
condition

I use the WixDifxAppExtension to install multiple drivers in configurations
where in most cases the hardware will not exist, because they are different
types of printer drivers and no hardware, or one model of printer is
expected. Maybe the difference is related to the DifxApp flags. In my
Component which includes the INF file as the keypath, I also have:
<difx:Driver AddRemovePrograms="no" PlugAndPlayPrompt="no" />



--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Difxapp-Compon
ent-Installation-condition-tp7600921p7600924.html
Sent from the wix-users mailing list archive at Nabble.com.

----------------------------------------------------------------------------
--
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------

[Phill Hogland]

I think it would be advisable to follow the one-resource-per-component
pattern.
http://stackoverflow.com/questions/1602831/wix-one-file-per-component-or-several-files-per-component



--
View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-deprecated-Difxapp-Component-Installation-condition-tp7600925p7600926.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------

[Marc Beaudry]

Ok, I'll modify my MSI accordingly... Thanks for the advice..


-----Original Message-----
From: Phill Hogland [mailto:***@rimage.com]
Sent: July-22-2015 4:59 PM
To: wix-***@lists.sourceforge.net
Subject: Re: [wix-users] (deprecated) (deprecated) Difxapp Component
Installation condition

I think it would be advisable to follow the one-resource-per-component
pattern.
http://stackoverflow.com/questions/1602831/wix-one-file-per-component-or-sev
eral-files-per-component



--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-deprecated-
Difxapp-Component-Installation-condition-tp7600925p7600926.html
Sent from the wix-users mailing list archive at Nabble.com.

----------------------------------------------------------------------------
--
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------