Microsoft Knowledge Base Email Alertz

The HTML events may not work correctly when a managed application tries to interact with an HTML document by using the MSHTML primary interop assembly component

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 934368 - Last Review: October 27, 2007 - Revision: 1.2

The HTML events may not work correctly when a managed application tries to interact with an HTML document by using the MSHTML primary interop assembly component in Internet Explorer

INTRODUCTION

Consider the following scenario. In Internet Explorer, a managed application tries to interact with an HTML document by using the MSHTML primary interop assembly (Microsoft.mshtml.dll) component. In this scenario, the HTML events may not work correctly. Typically, the MSHTML primary interop assembly component is incorporated into the Microsoft Visual Studio IDE for internal use. However, using the component in end-user applications is not supported.

Note This problem occurs in all the versions of Internet Explorer.

MORE INFORMATION

These are some known issues that are related to the MSHTML primary interop assembly:
  • When you use the Internet Explorer MSHTML.dll file in a Visual Studio .NET application, the MSHTML primary interop assembly may increase the redistributable file size. For more information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base:
    305622  (http://kbalertz.com/Feedback.aspx?kbNumber=305622/ ) Primary interop assembly for MSHTML increases size of redistributable file
  • You may be unable to register the MSHTML primary interop assembly by using the Global Assembly Cache tool (Gacutil.exe). Additionally, you may be unable to register the MSHTML primary interop assembly by using the Assembly Registration tool (Regasm.exe).

    For more information about how to install the MSHTML primary interop assembly, visit the following Microsoft Developer Network (MSDN) blog:
    http://blogs.msdn.com/infopath/archive/2004/09/27/234911.aspx (http://blogs.msdn.com/infopath/archive/2004/09/27/234911.aspx)
  • The managed applications may not work correctly because the MSHTML primary interop assembly is registered incorrectly on the computer.
  • Internet Explorer 6 may stop responding when you use the MSHTML primary interop assembly. Additionally, you may notice that Internet Explorer does not respond to some keyboard message events and some mouse message events.

STATUS

This behavior is by design.

APPLIES TO
  • Microsoft Internet Explorer 6.0
  • Windows Internet Explorer 7
  • Microsoft Internet Explorer 5.5
  • Microsoft Internet Explorer 5.01
  • Microsoft Internet Explorer 5.0
Keywords: 
kbinfo kbtshoot kbbug kbwebbrowser kbmshtml kbprb KB934368
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate