Could not load file or assembly 'Microsoft.mshtml, version=7.0.3300.0,Culture=neutral,PublicKey=b03f5f7f11d50a3a' or one of its dependencies. The System cannot find the file specified. The System cannot find the file specified. The global assembly cache (GAC) provides a centralised. If you are not using an installer, there are two easy ways to install an assembly to the GAC.
Mshtml Reference
I have a Chemical# solution that makes make use of of (I'm developing on the main project which utilizes this, therefore I don't understand very much about this collection), which can make a benchmark to MSHTML. This worked good until my upgrade to Windows 10 and it can't discover MSHTML anymore. I can directly reference the DLL ón the GAC foIder, and it stops complaining and therefore develops, but it's obtaining some runtime errors associated to the publisher not instantiating.
After a little research, it turns out that MSHTML is phased out of Home windows 10 as it today uses EdgeHTML. Does anyone have got any idea how I can move around this? The answer still functions for Windows 7. It is usually not 'phased out', MSHTML will be still intensely used in Win10. The Winforms and WPF WebBrowser lessons depend on it. Nothing is visibly incorrect with the COMReference is usually that.csproj file.
Attempt it óut with á dummy project, use Project >Add Benchmark >Browse button and select chemical: home windows system32 mshtml.tlb. If that drops over then you'll understand something else you can document in your query. At a minimal quote specific error communications and mention the Route property worth of the MSHTML benchmark. - Aug 6 '15 at 12:46. I simply made a on this concern. The problem will be that the Micrósoft.mshtml.dll assembly in the Global Assembly Cache turns into unregistered from ActivéX during the upgradé process.
To fix this problem, it is certainly essential to run 'regasm' on the assembly:. Open an example of 'Developer Command Prompt for VS2013' (or whatever version of Visual Facilities you happen to become using).
Run it as Officer by right-clicking the icon and selecting, 'Work as Officer.' . Navigate to 'D: Home windows assembly GAC Microsoft.mshtmI 7.0.3300.0b03f5f7f11d50a3a.' It is usually probable your route will vary. To confirm, move to 'Chemical: Home windows assembly GAC Microsoft.mshtml' and kind 'dir.' .
As soon as you are in the correct path, kind regasm Microsoft.mshtmI.dll. I experienced the same issue and I think what's i9000 heading on, at minimum in my case, will be that the project was originally a VS2012 project on Windows 7 and there was a main interop assembly installed that was referenced. When I removed and re-added the research to MSHTML and do a diff on the documents, the just difference had been that the has been changed from primary to tlbimp and has been transformed from false to accurate.
At some point, Visual Facilities added the capability to add the COM wrappers directly into the set up rather of referencing PIAs, therefore my think is that a fresh VS2015 set up on Home windows 10 no longer installs PIAs because they're also not necessary. So that's why eliminating and re-adding the benchmark repairs the problem and the task should keep on to build fine on old OS mainly because nicely. MSHTML is definitely nevertheless an essential component in Home windows 10, also with Edge as the default web browser. You can discover it in 'M: Windows Program32'. To estimate from the public Common questions: MSHTML: In Home windows 10 the WebBrowser control will make use of Web Explorer'h legacy object rendering engine, mshtml.dll. At this time EdgeHTML is certainly not accessible through the WebBrowser control. EdgeHtml In General Windows Apps built for Windows 10, the WebView handle use Microsoft EdgeHTML.
WebView handles in apps built for Home windows 8 8.1 will keep on to download the MSHTML to preserve compatibility.