![]() |
|
![]() |
Lack of decent driver support |
Possibly not as big an issue as it was now that you have the Driver Install Frameworks (DIFxAPP), however that is really just tacked on support rather than integrated, also see my "Microsoft Committed to Windows Installer?" point...
My Unanswered Questions - Too hard? |
I'm hoping that the fact that DIFxAPP doesn't display error dialogs on fatal problems is a "bug" and not a feature. As it is users won't know what to do and may not even notice the package has failed to install.
I didn't notice any flags for this...
It appears from the doco that I can't have the driver remain on the system on uninstall of the MSI, is that correct?
Normally to keep a resource on uninstall setting the components "ComponentId" column to null would do this however reading the doco (which I have already worked out is wrong in many ways) implies (but doesn't say) that this won't work.
My devices appear to be unloaded by the uninstall even though I did NOT set the flag which says to remove system driver files.
This issue is the only thing stopping me from using DIFxAPP to repackage drivers, I want to install updates to drivers and not have any uninstall processing effect the devices in any way. I want installation of a new driver to be applied to devices for which the driver is intended (basically no device activity at all during uninstall).
![]() ![]() |
| ![]() ![]() |