I am building an INF installer/uninstaller for a plugin for Internet Explorer who's original source is an MSI installer. I've converted heaps of MSI installers to INF ones before and never had any problems like this before, and it seems to me that the source of my issue can only be in one of two places - a required MSI setting or an IE setting which I've overlooked.
First of all, I can confirm in both a local install and a VM install (using virgin copy of win2k3) that all of my INF stuff is both installing and removing all the exact same reg entries/files as the native MSI installer does - with the exception of any specific MSI related reg code. But after my INF install, when I open up Internet Exporer to activate the browser plugin it does not show up as listed in View\Explorer Bar where it should....
I take a regshot and then run the native MSI installer OVER the top of my already existing INF installation and the ONLY new things that the MSI installer is adding to my registry is the following code sections, after which the browser plugin then becomes visible in View\Explorer Bar where it should. No other settings for internet explorer have changed anywhere, just these new sections are added:
Code: Select all
HKLM\SOFTWARE\Classes\Installer\Features\............ HKLM\SOFTWARE\Classes\Installer\Products\............ HKLM\SOFTWARE\Classes\Installer\UpgradeCodes\.......... HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\........... HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\.............
1. Is there some particular thing that any of these sections of extra MSI-related code might contain something which somehow "authenticates" the plugin as being "OK for IE to use" - perhaps come kind of security code which makes it "approved" by windoze?
2. Could the problem be somewhere in the realms of the possibility that the plugin will not be authorised to operate unless it can check back to the registry to look for some code which relates to the "repair" feature of the MSI installer - which as far as I can tell is redundant because I've done regshot comparisions of what happens from the native MSI installer when you run "repair" and it does not alter any of the files or reg entries in any way whatsoever.
3. Or could it be nothing to do with the MSI installer at all, and that I have totally overlooked some other change in the registry which is silently modified (rather than added or deleted) to do with activating/displaying IE browser plugins - but it beats me how I could have missed that though, with the number of different ways I have run and compared my reg shots
I'd really appreciate it if anyone here who has had experience making addon (not switchless) installers for IE plugins might be able to shed some light on the subject for me.
Thanks for reading.