Navigate to 'C: Windows assembly GAC Microsoft.mshtml.Run it as Administrator by right-clicking the icon and selecting, 'Run as Administrator.' Open an instance of 'Developer Command Prompt for VS2013' (or whatever version of Visual Studio you happen to be using).To fix this issue, it is necessary to run 'regasm' on the assembly: The problem is that the assembly in the Global Assembly Cache becomes unregistered from ActiveX during the upgrade process. At a minimum quote exact error messages and mention the Path property value of the MSHTML reference. If that falls over then you'll know something else you can document in your question. Try it out with a dummy project, use Project >Add Reference >Browse button and select c: windows system32 mshtml.tlb. Nothing is visibly wrong with the COMReference is that.csproj file. The Winforms and WPF WebBrowser classes depend on it. It is not 'phased out', MSHTML is still heavily used in Win10. Does anyone have any idea how I can go around this? The solution still works for Windows 7. After a little research, it turns out that MSHTML is phased out of Windows 10 as it now uses EdgeHTML. 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. This worked fine until my upgrade to Windows 10 and it can't find MSHTML anymore. I have a C# solution that makes use of (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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |