|WikiProject Computing / Software||(Rated Start-class)|
|WikiProject Microsoft Windows / Computing||(Rated Start-class, Mid-importance)|
MSXML 3.0 has namespace MSXML2, but MSXML 2.5 has namespace MSXML. Thus they are not compatible. It is required to verify correctness of "CLSIDs and ProgIDs it exposes have been subsumed by MSXML 3.0" AZiubin (talk) 16:20, 3 November 2009 (UTC)
I have found that TYPELIB resources of msxml.dll includes "namespace MSXML", but in msxml3.dll it includes "namespace MSXML2", so MSXML 2.5 and MSXML 3.0 have incompatible type libraries, which is critical for compiling phase. I have verified that program (or dll library), which compiled with MSXML 2.5 type library can run with MSXML 3.0 installed. AZiubin (talk) 16:58, 3 November 2009 (UTC)
I realize that an article titled MSXML is bound to be pretty technical in nature but I'm wondering if it could be somewhat less so.
For example, would it be reasonable to expect the article to address the questions "is it safe to uninstall MSXML from a Windows XP system?" "What might stop working if MSXML is uninstalled?"
Please open a new section in order to discuss the security importance of that piece of code in modern Microsoft OS's since Vista (7,8). There is an urgent update for this core code as well as the core of Visual Studio among others in order to quickly close some fatal open in-hooks. Please give us a comprehensible view of embedding this parts (XML cores) in that modern design (W7,8) Thanks for your really important work to bring enlightning in a quick changing IT world... --Cosy-ch (talk) 07:02, 22 January 2013 (UTC)