Comments by MrT33 (Top 4 by date)

One possible solution we are thinking about to support both MSHTML (for pre Win 10) and EdgeHTML (for Win 10) is to implement a API interface for all MSHTML COM calls in a C++ DLL (which we ship on pre Win 10), and implement the equivalent for EdgeHTML in another DLL (which we ship on Win 10). The application would then load the DLL appropriate for the OS it is running on.

The problem we have is to get started with EdgeHTML, ie, embed it in an application as an HTML editor and finding documentation for an interface to the equivalent of what the MSHTML COM interface offers.

We are currently using Microsoft Visual Studio 2013 for our entire program suite.

There is also the fear that MSHTML one day will disappear from Windows 10.

Thank you :)

We want to take advantage of HTML5 standards and make them available to our users. MSHTML embedded in an application doesn't do this by default. The changes required to get MSHTML to support HTML5 standards are fairly large due to the original design many years ago, a design deeply embedded in the product.

We are hoping that a move to EdgeHTML will make HTML5 standards available, but we need to test it first.

We can not rewrite the application from scratch. We need to replace MSHTML with EdgeHTML in the existing application. And yes, we are aware that EdgeHTML is only supported on Windows 10 and we will need to keep using MSHTML on previous version of Windows.