In MSHTML the interfaces are often numbered. The numbers are at the end of the interface names like IHTML{name}{number}. Interfaces like:
IHTMLRuleStyle
IHTMLRuleStyle2
...
IHTMLRuleStyle6
or
IHTMLElement
IHTMLElement2
...
IHTMLElement7
A list can be seen in this Microsoft page
Thanks #Jay for your comments.
The numbers represent the version of MSHTML and the version numbers have an indirect relationship with the version of Internet Explorer, CSS, HTML, etc...
I wish I had did this search before but Geoff Chappell's site has a great chart mapping versions of MSHTML to IE and Windows.
Versions of things
MSHTML IE Windows
6.0 6.0 Windows XP
6.0 6.0 Windows Server 2003
7.0 7.0 Windows Vista
8.0 8.0 Windows 7
Judging from the chart, the version of MSHTML is closely related to the version of Internet Explorer.
Related
I have a universal windows application for windows 8.1 and windows phone (WAP)
But my customer doesn't have access to the windows store, there's a way to use Installshield or something similar to generate a Setup Installer?
At the moment i have to type some code in powershell and it's really annoying and unprofessional.
There's a workaround for this situation?
The Suite/Advanced UI project type (Premier edition of recent enough versions—probably 2012 Spring) has support for side-loading .appx packages. More recent versions (2016 or so) add support for Windows 10 UWP App Packages.
I see that the Interactivity namespace was moved into the Prism.Wpf package since V6 - how do I access this functionality in a Win10 UAP app?
Prism.Wpf is for WPF only and thus not compatible with Windows 10 UWP (binary wise).
For Windows 8.1 RT / Windows 10 UWP you currently can add a reference to the Behaviors SDK. Note that it targets Windows 8.1, but it works under Windows 10 as well.
An alternative to adding the reference is opening Blend, and dragging a behavior from the Assets tab onto your page. This will add a reference as well.
Even better news is that Microsoft is working on a NuGet library for Windows 10 UWP behaviors, which should be available in approx. 1 month and will be made open source. So anyone reading this in the future, should look for the package.
What are the system requirements for vscode?
The download page only shows the different platforms this is available on, but doesn't mention any requirements such as Windows version (i know it doesn't work on XP) or additional required components, such as the .NET framework.
System requirements for VSCode are available on the documentation page.
In a nutshell, VSCode now is self contained for Linux, Mac and Windows. There is a complete list for the additional helpful tools available on the setup page.
It's not listed in their requirements, but you'll also need a decent video card. It may seem ridiculous, since it's mainly displaying text, but vscode's GPU hardware requirement is well beyond what other applications require. There is a switch --disable-gpu to switch it to software rendering but it's still laggy.
As of Version 1.32
1.6 GHz or faster processor with 1 GB RAM recommended
OS X Yosemite
Windows 7 (with .NET Framework 4.5.2), 8.0, 8.1 and 10 (32-bit and 64-bit)
Linux with GLIBCXX version 3.4.15 or later, GLIBC version 2.15 or later, tested with Linux (Debian): Ubuntu Desktop 14.04, Debian 7, Linux (Red Hat): Red Hat Enterprise Linux 7, CentOS 7, Fedora 23
I've installed Google Web Designer on Windows XP, and saw this error:
The procedure entry point GetSystemDefaultLocaleName could not be located in the dynamic library KERNEL32.dll
What can I do?
I think that it won't support XP.
Here are the minimum system requirements, according to their documentation:
Operating system
Windows requirements
Windows 7
Windows 8
I think it does not support Windows XP. I installed in Windows 7. No issues. The error you have got is mainly caused by misinterpreted operating system -- that's described as a possible cause in Microsoft's support knowledge base:
The application is misinterpreting the operating system version and is trying to call a procedure in the Windows 95 or Windows 98 version of the Dynamic Link Library (DLL) that is unavailable in Windows NT version 4.0 or Windows 2000.
Windows XP is not supported. See the system requirements.
XP isn't a supported OS for .NET 4.5. This is a known issue.
I read a few months back that the reason XP can't install 4.5 is because there are kernel API that 4.5 calls which don't exist on XP. I also read that it would be possible to inject your own implementation of the 'new' kernel calls to an XP machine - and 4.5 could run.
I can no longer find this information. Does anyone know more about this?
A second, but related, question is - how can I take upgraded .Net 4.0 libraries from a windows 7 machine (which had 4.5 installed) and inject them into an xp machine? I believe I read that the implemention files of 4.5 are actually the same as the 4.0 files, there are not two sets. And in fact, the two .net folders (4.0 and 4.5) are only the interfaces - which link back to these same files. If this is the case, then a manual injection of the 4.0 files would likely need the solution to my first question.
In short - does anyone have more information about hacking/manually upgraded .net for xp?