In response to #2: It looks like you are using the same / similar hardware
that we do. We also use an FTDI product (FT232R). However, there are some
differences:
(a) We use our own product code so as not to mix the device up with normal
FTDI devices.
(b) As a consequence, we renamed and modified the standard INF files while
following the documented FTDI procedures for doing so. The result has not
yet been signed.
(c) Our WiX fragment is nearly identical to yours. The DIFxApp element is
as follows:
<difxapp:Driver DeleteFiles="no" ForceInstall="no"
Legacy="yes" PlugAndPlayPrompt="no" AddRemovePrograms="yes" />
The key differences between our elements seems to be "ForceInstall"
attribute and "AddRemovePrograms" attribute. Also the use of the Legacy
attribute. Did you find these made much of a difference? Reading the
MsiDriverPackages table documentation, I can't imagine it would:
http://msdn.microsoft.com/en-us/library/ff549362(VS.85).aspx.
ForceInstall "configures DIFxApp to force the installation of a new PnP
function driver on a device, even if the driver that is currently installed
on a device is a better match than the new driver" so did not seem to be
desirable. Also it doesn't seem like it would be applicable in this case,
since the sequence is uninstall then reinstall (i.e. when installing, no
driver is installed at all so the value of ForceInstall would be ignored?)
The one reason I have read for having AddRemovePrograms="yes" is so that the
driver can be removed from Safe Mode (apparently MSI can't be invoked from
Safe Mode). Is this still good advice? Otherwise it just seems like
unnecessary clutter in ARP.
DeleteFiles="no" is the default; I included it anyway just to be explicit.
Documentation says it's not supported any more on Windows 7...
Best regards,
James Johnston
-----Original Message-----
From: Quinton Tormanen [mailto:quint...@deltamotion.com]
Sent: Monday, November 29, 2010 22:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DIFxApp and upgrades
2. I do not see the second problem at all with our driver install. Any
devices that are plugged in are "immediately" available with the new drivers
after the install completes. In rare cases the user will be asked to restart
the PC. Are your drivers digitally signed? Here is what our WiX looks like
for the DifxAppExtension component. I did have to play around with the the
DIFxApp options (now encoded in the difxns:Driver element) back when we
first developed the driver to get the behavior I wanted.
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
