We've got a shell extension which hooks into Explorer.exe menus for our stuff.
It installs ok using a WiX fragment I generated using heat.exe. But when I try to upgrade it (major upgrade), the "files in use" dialog displays and says that it must stop explorer.exe to update the files, and it gives an option to have the application restarted after update is complete. Sometimes users pick the wrong option there and explorer.exe doesn't restart, and they are screwed because they don't know what to do next. It's even worse if they are lowly users. I had authored in a couple of regsvr32 custom actions which had impersonate=no specified, (because the user has to have provided elevated creds already). I could get those to run at an early enough time to unregister the extension before MSI looked for files in use, but that is not good for lots of reasons. Things are broken if the user exits the installer before I can re-register it, etc.). So I thought if I used heat to generate the right stuff, then maybe 'files in use' wouldn't occur for the extension because it "knows" that we have registration information authored in. How can I uninstall a shell extension without having to shutdown explorer? Thanks for any guidance... BTW - I'm using WiX 3.5.2519 -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Registering-Explorer-Shell-Extension-using-Heat-tp7584406.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
