How To Install Microsoft.Mshtml Assembly
Chang the files Microsoft.mshtml.dll from 'Prerequisite' to 'Include' and republish the project. Jump to Method 3: Doing a Clean Reinstall of the Software That Is Giving the. - Following the verification and instructions for the software uninstall. File or assembly name Microsoft.mshtml, or one of its dependencies, was not. Ps: yes the customer *has*.net 1.1 and infopath sp1 installed;-).
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?
Software WindLDR. Even without ladder program experience, you can use the built-in editors, shortcuts and. Classes, we guaranteed you come away with full knowledge of WindLDR and IDEC PLCs. What's new in WindLDR version 6? Windldr programming software: full version software. WindLDR v5.x is the previous version of the IDEC PLC programming software. This version is still available for purchase for programming of older IDEC PLC.
The solution still works for Windows 7.
6 Answers
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:
- Open an instance of 'Developer Command Prompt for VS2013' (or whatever version of Visual Studio you happen to be using). Run it as Administrator by right-clicking the icon and selecting, 'Run as Administrator.'
- Navigate to 'C:WindowsassemblyGACMicrosoft.mshtml7.0.3300.0__b03f5f7f11d50a3a.' It is possible your path will vary. To verify, go to 'C:WindowsassemblyGACMicrosoft.mshtml' and type 'dir.'
- Once you are in the correct path, type
regasm Microsoft.mshtml.dll
I had the exact same problem. Adding the c:windowssystem32mshtml.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 :)
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 from primary to tlbimp and <EmbedInteropTypes> was changed from false to true.
Mshtml Assembly
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.
MSHTML is still an important component in Windows 10, even with Edge as the default browser. You can find it in 'C:WindowsSystem32'. To quote from the official FAQ:
MSHTML:
In Windows 10 the WebBrowser control will use Internet Explorer’s legacy rendering engine, mshtml.dll. Online pipe organ simulator. At this time EdgeHTML is not available through the WebBrowser control.
EdgeHtml
Mshtml Download
In Universal Windows Apps built for Windows 10, the WebView control use Microsoft EdgeHTML. WebView controls in apps built for Windows 8 & 8.1 will continue to load the MSHTML to preserve compatibility.
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.
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 following cd C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEPublicAssemblies. Then regasm Microsoft.mshtml.dll.