Currently I am having problems registering a WMI interface during a product upgrade. Currently I am using a custom action to directly access the exported functions in the file "InstallUtilLib.dll". Everything functions as expected on a new install but when the product is upgraded but the wrong version the interface is getting registered. The screwy thing is that if you run a repair on the install, the registration process goes through and completes correctly and the correct files get copied into place and the interface functions.
Right now I have no idea where the WMI interface is getting the older version and why the new version is not being copied correctly. Right now the DLLs that control the custom WMI interface are installed in the products target folder. No files are copied into the GAC by any process in the install. The registration process for the WMI interface is run against the file in the installation folder. A coworker and I have both hunted the web for any information on how WMI interfaces are registered and also for possible alternatives to using "InstallUtilLib.dll". We have not been able to any alternative and this is not like COM interop where you can just put the registry values into in place and everything is happy. Does anyone have any incite as to what happens during WMI registration? Is there a better way than using "InstallUtilLib.dll"? Any help would be greatly appreciated, Mat Skildum ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
