Clarification about Microsoft.mshtml component within .NET 2 frame

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Filippo Bettinaglio - 12 Mar 2006 20:25 GMT

Hi all,

In the past 3 days I have done some research about Microsoft.mshtml
component within .NET 2 framework.

I need some clarification/comfermation about the Microsoft.mshtml componet
and microsoft stargey. In specific: Microsoft.mshtml within the .net 2
framework

1.    mshtml.HTMLDocument is not part of the .net 2 framework.

2.    it seems that microsoft suggests to use .net managed classes. E.g.
System.Windows.Forms.HtmlDocument instead than mshtml.HTMLDocument

3.    Those new classes works fine with the web control (because is managed)
but they are limited in the use, specifically in interfacing with Internet
Explorer 6 and IE7 Beta 2. (e.g. I cannot access from a C# user control the
DOM of the HTML in which the control is hosted)

Can someone comment the above 3 point? Are they correct?

Next question:

Which are the implication redistribuiting the Microsoft.mshtml with a .NET 2
applications?

Is it only a metter of distribuiting the file (8 MB) with my application? Or
is there anything else?

Many Thanks,

FILIPPO

Reply to this Message

Dmytro Lapshyn [MVP] - 13 Mar 2006 15:27 GMT

Hi,

> 1. mshtml.HTMLDocument is not part of the .net 2 framework.

No, it apparently isn't.

> 2. it seems that microsoft suggests to use .net managed classes. E.g.
> System.Windows.Forms.HtmlDocument instead than mshtml.HTMLDocument

I haven't seen such suggestions (which however does not negate their
existence). Anyway, if there's something in the Framework already, I'd try
it first before resorting to any interaction with unmanaged code. I suppose
that System.Windows.Forms.HtmlDocument is only a wrapper around
mshtml.HTMLDocument, but this is kind of a blind (or educated, if you wish)
guess.

> 3. Those new classes works fine with the web control (because is managed)

I really doubt the Web control is managed. Most likely it is just a wrapper
around the IE's ActiveX control.

> but they are limited in the use, specifically in interfacing with
> Internet
> Explorer 6 and IE7 Beta 2. (e.g. I cannot access from a C# user control
> the
> DOM of the HTML in which the control is hosted)

This might be possible. You can try to access DOM by using late binding (VB
.NET seems to have a native support for it, whereas in C# you'll have to use
reflection).

> Hi all,
>
[quoted text clipped - 32 lines]
>
> FILIPPO

Reply to this Message

Clarification about Microsoft.mshtml component within .NET 2 frame

Free Magazines