Article ID: 176792 - View products that this article applies to.
This article was previously published under Q176792
It is possible to connect to a running instance of Internet Explorer version 4.0 or later using the SHDocVw.ShellWindows collection.
Typically, an application connects to a running instance of another application using the Running Object table. Because Internet Explorer 4.0 does not register itself in the running object table, another method is necessary.
The ShellWindows collection is described in the Internet Client SDK as follows: The ShellWindows object represents a collection of the open windows that belong to the shell. In fact, this collection contains references to Internet Explorer as well as other windows belonging to the shell, such as the Windows Explorer.
The following Visual Basic code obtains a reference to the ShellWindows collection. The collection is enumerated and the LocationName for each object added to a list box. If the document associated with the object is of type HTMLDocument (a Web Page), the title for the page is added to another list box.
To run the following code, it is necessary to add a reference to "Microsoft Internet Controls" (Shdocvw.dll) and "Microsoft HTML Object Library" (Mshtml.dll) to the Visual Basic project:
In C++, a connection can be accomplished in roughly the same way. Visual C++ Native Com Support is used here for the sake of brevity.
Add references to Shdocvw.dll and Mshtml.dll to the project:
Declare an instance of an IShellWindows pointer in your view class:
Create an instance of a ShellWindows object in your view's constructor:
Use the ShellWindows object in your view's OnInitialUpdate function:
The previous method for connecting to a running instance of the Internet Explorer does not work if Shell Integration is not installed or if "Browse in a new process" is selected in Internet Explorer 4.0.
If these factors cannot be controlled, there is still one possible method that may work. A browser helper object can be written to register Internet Explorer 4.0 in the running object table (ROT). There are many implementations possible here depending on how the application is to determine the instance of Internet Explorer with which to connect. This is just one possible solution: The browser helper object, having access to the object model of the instance of Explorer that launched it, would determine if this is the instance of the browser that should be registered in the running object table.
The interface that the consumer is interested in can be registered in the ROT with the RegisterActiveObject function and a dummy CLSID that the consumer will recognize. Another solution, that would allow multiple instances of the explorer to be registered in the ROT, would be to have the Browser Helper object compose an Item moniker based on a GUID and piece of data unique to each instance of Internet Explorer. The moniker would be registered in the ROT with the IRunningObjectTable::Register method. Again, the consumer would have to know how recognize this moniker.
For more information, please visit the MSDN Online Web Workshop at:
MSDN LibraryThe Internet Client SDK; search on Internet Tools and Technologies - Windows Shell API
For additional information, please see the following article in the Microsoft Knowledge Base:
179230For more information, please visit the following article at:
(http://support.microsoft.com/kb/179230/EN-US/ )FILE: IEHelper-Attaching to IE4 using a Browser Helper Object
http://msdn2.microsoft.com/en-us/library/Bb250436.aspx(c) Microsoft Corporation 1997, All Rights Reserved. Contributions by Robert Duke, Microsoft Corporation