Driver Element (Difxapp Extension)

Windows Installer XML (WiX) v3.0

Driver Element (Difxapp Extension)

Description
Installs a driver. To use this element, you need to reference the WixDifxAppExtension extension and add the .wixlib appropriate for the target platform (difxapp_x86.wixlib, difxapp_x64.wixlib, or difxapp_ia64.wixlib) to your project.
Windows Installer references
None
Parents
Component
Inner Text
None
Children
None
Attributes
Name Type Description Required
AddRemovePrograms YesNoType Specifies that the DIFxApp CustomActions should add an entry in the Add/Remove Programs Control Panel applet. The default is 'yes'.  
DeleteFiles YesNoType If set to "yes", configures DIFxApp to delete binary files that were copied to the system from the driver store when a driver package was installed. If this attribute is set to "no" or not present, DIFxApp does not remove these files from a system. Note that configuring DIFxApp to delete these files is controlled by the Flags entry value of the component that represents the driver package in the MsiDriverPackages custom table. Setting DriverDeleteFiles to "yes" sets the corresponding bit in the Flags entry value. Setting DriverLegacy to "no" clears the corresponding bit in the Flags entry value. If this attribute is not present, DIFxApp uses a default value of "no".  
ForceInstall YesNoType Specifies that the DIFxApp CustomActions should force the installation of a new Plug and Play driver on a device, even if the currently installed driver on the device is a better match than the new driver. Specifying 'no' is an excellent way to ensure the DIFxApp CustomActions recognize the Component contains a driver for installation. The default is null which means the Component does not install a driver via DIFxApp CustomActions. See http://www.microsoft.com/whdc/driver/install/difxtools.mspx for more information.  
Legacy YesNoType If set to "yes", configures DIFxApp to install unsigned driver packages and driver packages with missing files. For more information, see "Installing Unsigned Driver Packages in Legacy Mode" earlier in this paper. If this attribute is set to "no" or not present, DIFxApp will install only signed driver packages. Note that configuring DIFxApp to install unsigned drivers is controlled by the Flags entry value of the component that represents the driver package in the MsiDriverPackages custom table. Setting DriverLegacy to "yes" sets the corresponding bit in the Flags entry value. Setting DriverLegacy to "no" clears the bit in the Flags entry value that configures DIFxApp to install unsigned driver packages. If this attribute is not present, DIFxApp uses a default value of "no".  
PlugAndPlayPrompt YesNoType Specifies that the DIFxApp CustomActions should prompt the user to connect the Plug and Play device if it is not connected. The default is 'yes'.  
Sequence Integer Specifies an optional installation sequence number. DIFxApp CustomActions install the driver packages in an installation package in the order of increasing sequence numbers. The same sequence number can be used for more than one driver; however, the order in which packages with the same sequence number are actually installed cannot be determined.  
See Also
Difxapp Schema