MSHTML question using C#

hmmm i Hope you are familiar with how to actually use the WebBrowser control in a C# application,

Now i was thinking that since IWebBrowser2 interface derives from IDispatch you will already have the definition of IDispatch in ur project so you might be able to use that.

Also for the constants like the ones below you will have to use the VS.Net Object browser to see if they are exposed as enumerated types, otherwise you will have to look up the header files and hand code the values of these constants.
DLCTL_DLIMAGES, DLCTL_VIDEOS, and DLCTL_BGSOUNDS
DLCTL_NO_SCRIPTS and DLCTL_NO_JAVA
DLCTL_NO_DLACTIVEXCTLS and DLCTL_NO_RUNACTIVEXCTLS:

Well i just went through the interfaces by importing the webbrowser control into a project and using "Object browser"

it seems you will have to import IDispatch seperately, you will have to use header files to get the values of the constants and most probable making the form which hosts the control implement IDispatch should do the trick.

IDispatch is defined in oaidl.idl , look for that file in your system then use "midl.exe" to create a type library and then use "tlbimp.exe" to create a RCW. now you are ready to use the IDispatch interface

for more information on this step check out
http://www.codeproject.com/csharp/advhost.asp

and also some other good articles on using WebBrowser control with .Net on the same site by the same author

Thanks for the info, Sijin, I will check it out.  I am making the transition from C++ to C# so I may be a bit slow in doing this but rest assured I'll post another comment or award points in a few days.

Thanks!

The main problem you will run into is that the IDispatch implementation must be for the host of the WebBrowser control.

I originally thought you might be able to override the Invoke implementation, just like Sijin, however, IDispatch is not implemented by .NET objects.  In fact, what you will need to do is hook into the COM Callable Wrapper (CCW) to intercept the call to Invoke and handle it accordingly.

I wish there were a more elegant solution.  I even wrote Chris Sells to see if he knew of a better approach.  Unfortunately, I don't think there is.

Sorry,

Bg

I would like to know how you finally managed to do it? :)

Same here.

I can't say that it is completely working yet, but I didn't want to leave the question open forever.  I am in the process of using ATL to write a wrapper and use it as a sort of "intermediary" between C# and COM.  If this doesn't work I'm going to drop to managed C++.  With the release of Visual Studio 2003 beta I can use Winforms but still get some low-level access to COM components from what I've been reading.