I install the CP210x driver. The approach I take is to create a msi package
and use WixDifxAppExtension. I use a single project to build both x86 and
x64 packages. This is one example (although I would revise several details,
like using InstallerPlatform):
http://alekdavis.blogspot.com/2011/05/build-32-and-64-bit-installers-using.html
Specifically in regard to creating an msi to deploy the CP210x driver the
WixDifxAppExtension seems to require that Product/@Manufacture be the same
as the Manufacture set in the INF file ("SiLabs"). I set
Package/@Manufacture to my company with Package/@Comment indicating why I
set Product/@Manufacture to a different company name. Other than that
detail the call to difx in the INF file element is just:
<difx:Driver PlugAndPlayPrompt="no" />
By creating a 64 bit msi, on x64 systems, the msi will cache the driver's
files in a x64 location and then execute the 64 bit version of difxapp.dll.
I'm not sure if this is possible when a 32 bit bundle caches the files
directly (even if there was no issue with the Payload behavior).
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Payload-not-copying-inf-tp7597985p7597990.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
