I'm writing an installer for a WDF driver, and am finding that MsiProcessDrivers is being run after files have been removed. The problem is that according to the documentation, I need to run WdfPostDeviceRemove() after the service has been deleted - which requires WdfCoInstaller01009.dll to be loaded. Since that's already been deleted, my custom action is failing. Should I be scheduling MsiProcessDrivers earlier in the InstallExecute sequence, or do people just avoid DIFx and use DPinst etc. for drivers?
-- Bruce Cran ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
