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-Difxa
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.
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
Compon
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
This mailing list has moved. Please sign up for the
wix-us...@lists.wixtoolset.org mailing list.
More information can be found here:
https://www.firegiant.com/blog/2015/7/21/new-wix-mailing-lists/
--
___
My build process creates a bundle output folder tree with the sub folder
"x64" and "x86" under which there are platform specific driver packages:
bundle.exe
MSI1_Folder
MSI2_Folder
x64
Driver1Folder
Driver2Folder
x86
Driver1Folder
Driver2Folder
I have a situation where I need to cr
"Util RegistrySearch has an attribute Winb64 that seems to be no by default.
If this is set to Yes, Would it mean it would look in the 32 bit registry
on 32bit OS and 64bit registry on 64 bit OS ? "
Yes. but the attribute is RegistrySearch/@Win64. In the default situation
where it is no or doe
7 matches
Mail list logo
