I have a C# solution that makes use of Smith Html Editor (I'm developing on the main project which uses this, so I don't know much about this library), which makes a reference to MSHTML. This worked fine until my upgrade to Windows 10 and it can't find MSHTML anymore. I can directly reference the DLL on the GAC folder, and it stops complaining and thus builds, but it's getting some runtime errors related to the editor not instantiating.
After a little research, it turns out that MSHTML is phased out of Windows 10 as it now uses EdgeHTML. Does anyone have any idea how I can go around this?
The solution still works for Windows 7.
MSHTML is still an important component in Windows 10, even with Edge as the default browser. You can find it in "C:\Windows\System32". To quote from the official FAQ:
http://dev.modern.ie/platform/faq/will-the-webbrowser-control-work-with-mi
MSHTML:
EdgeHtml
I just created a blog post on this issue. The problem is that the Microsoft.mshtml.dll assembly in the Global Assembly Cache becomes unregistered from ActiveX during the upgrade process. To fix this issue, it is necessary to run "regasm" on the assembly:
regasm Microsoft.mshtml.dll
For some reason in my case the
Microsoft.mshtml
file was located in a different directory. On Visual Studio, double click the assembly reference, and you'll find the path to it. Now open the "Developer Command Prompt for VS2017", type the followingcd C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\PublicAssemblies
. Thenregasm Microsoft.mshtml.dll
.Using VS 2015 I had this issue after the last Windows 10 update. I removed the reference "Microsoft HTML Object Library" and added it again to the project. This resolved the issue in my case.
I had the same issue and I think what's going on, at least in my case, is that the project was originally a VS2012 project on Windows 7 and there was a primary interop assembly installed that was referenced. When I removed and re-added the reference to MSHTML and did a diff on the files, the only difference was that the
<WrapperTool>
was changed fromprimary
totlbimp
and<EmbedInteropTypes>
was changed from false to true.At some point, Visual Studio added the ability to embed the COM wrappers directly into the assembly instead of referencing PIAs, so my guess is that a new VS2015 installation on Windows 10 no longer installs PIAs because they're not necessary. So that's why removing and re-adding the reference fixes the problem and the project should continue to build fine on older OS as well.
I had the exact same problem. Adding the c:\windows\system32\mshtml.tlb worked. Note it's NOT the dll, but the tlb. Thank you so much for asking this question and thank you Hans, for the answer :)