ieframe.dll failed to register
I have an Outlook add-in written in VS2005 (VSTO 2005, not SE) targeted at Outlook 2003.
The add-in contained a reference to the Web Browser Control because the add-in allows the user to click a link that will open up a browser window to a page in an intranet ASP.Net application that is related to the Outlook email or contact record.
However, when IE7 got pushed to my development machine, the reference to the Web Browser Control got changed to include the new ieframe.dll in the setup project.
However, when I run the setup.exe on another machine, I get the error:
Module c:\program files\my add-in\ieframe.dll failed to register. HRESULT -2147467263.
Has anyone run into this before? What's the proper way for dealing with this?
I also was adding a permission set for the
Interop.SHDocVw.dll
[893 byte] By [
DavidH.] at [2007-12-27]
Here's an update ..
In the Setup project associated with my Outlook add-in solution, I excluded from the Detected Dependencies section the reference that had automatically been added to ieframe.dll after the IE 7 upgrade. I have a separate reference to Interop.SHDocVw.dll, which I've kept included.
My custom CaspolSecurityPolicyCreator class in my associated SetSecurity project still adds the extra permission set for the Interop.SHDocVw.dll reference.
So with these changes, I can now get my Outlook add-in to install properly on a deployment machine that, too, has IE 7 installed. I haven't tried it yet on a machine that's still on IE6.
Any additional advice on this would still be appreciated.
Hi David.
You need to recompile the app on a computer running IE6, or else install IE7 on the target computer and try again. (Or redevelop the app / plugin to not use an embedded IE frame...)
Just came across a similar issue - Googled and came up with the answer. It's going to become a more prevalent problem now IE7 is getting out to developer's desktops, because most corp environment users will not know how to upgrade without having their SOE changed.
HTH
Brad
