Hi,

I am pretty sure Microsoft.mshtml has never been a part of .NET Framework.
Do you have any references that make you think otherwise?

I believe you cannot redistribute mshtml.dll alone - this is just not
permitted to do so from the licensing standpoint. As far as I remember, it
is a part of Internet Explorer, and you should require your users to have an
appropriate version of IE installed. On the other hand, .NET Framework
itself requires IE 5 or higher so unless you use something really advanced
available only in IE6 or IE7, you should be on the safe side here.

Now that I saw your original post with the detailed description of the
problem with the hosted C# control, I believe I can finally explain what is
going wrong in your scenario!

You are using the following code snippet in your C# control:

<code>
private System.Windows.Forms.HtmlDocument DocVal;

public System.Windows.Forms.HtmlDocument Doc
{
  get { return DocVal; }
  set
      {
        DocVal = value;
      }
}
</code>

This means that you expect the host (namely, IE) - to be more specific, the
JavaScript "loadDoc" function on the HTML page that contains your control,
to pass you an instance of System.Windows.Forms.HtmlDocument. But this is
plainly impossible - the JavaScript code knows nothing about the
HtmlDocument .NET wrapper! Yes, this is a wrapper - MSDN for VS 2005 reads
"HtmlDocument is a wrapper for the Internet Explorer Document Object Model
(DOM), which is written in COM.".

The "document" object you are passing is a COM object - namely
"mshtml.IHTMLDocument2", so the Doc property should be of  exactly the same
type (if "mshtml.HTMLDocument" works for you too, feel free to use it).

Now, Microsoft hasn't "dropped" mshtml.HTMLDocument from the Framework.
Again, I refer to MSDN:

"To use the unmanaged interfaces, import the MSHTML library (mshtml.dll)
into your application. However, you can also execute unexposed properties
and methods using the IDispatch::Invoke method.". So feel free to use the
tlbimp.exe utility to create an interop assembly for mshtml.dll and
reference the resultant interop assembly from your project.

Well, the explanation above is indeed somewhat vague, feel free to follow up
with more requests for clarification.