Which version of MSXML should I use?
Solution 1:
If you need to support Windows OS versions prior to Win2k, then use MSXML3. Otherwise, use MSXML6.
MSXML4 is in maintenance mode.
MSXML5 was never actually supported for use outside of MS-Office.
See:
- List of Microsoft XML Parser (MSXML) versions
- Using the right version of MSXML in Internet Explorer
Solution 2:
I had to make the same decision in my work a couple of years ago.
The MSDN states that version 6 is the optimal one to use, however they don't provide merge modules in the SDK and you are not allowed to distribute it in your application as you could with version 4. Version 4 was superceded by version 6 and version 5 was specifically for MS Office. Version 3 remains the target version on older machines.
What I ended up doing was taking a graceful degradation approach and attempting to use 6 first, failing that version 4, then failing that use version 3 (code is C++):
inline bool CXMLDocument::CreateXMLDOMFactory(void)
{
wxMutexLocker lock(sm_mXMLDOMFactory);
if(!sm_pXMLDOMFactory)
{
::CoGetClassObject(CLSID_DOMDocument60, CLSCTX_ALL, 0, IID_IClassFactory, reinterpret_cast<void **>(&sm_pXMLDOMFactory));
if(!sm_pXMLDOMFactory)
{
::CoGetClassObject(CLSID_DOMDocument40, CLSCTX_ALL, 0, IID_IClassFactory, reinterpret_cast<void **>(&sm_pXMLDOMFactory));
if(!sm_pXMLDOMFactory)
::CoGetClassObject(CLSID_DOMDocument30, CLSCTX_ALL, 0, IID_IClassFactory, reinterpret_cast<void **>(&sm_pXMLDOMFactory));
}
}
return sm_pXMLDOMFactory != 0;
}
We noticed measurable performance improvements after moving to version 6 from version 4, although you have to explicitly set the NewParser
property on the document to get this benefit, e.g.:
pDocument->setProperty(_bstr_t(L"NewParser"), VARIANT_TRUE);
There were also a couple more hoops to jump through when loading documents due to security considerations, remote DTDs and so on. Again, this was done via properties on the document, so it is worth looking up the ProhibitDTD
, UseInlineSchema
, AllowXsltScript
and ServerHTTPRequest
properties in the MSDN to see if they apply to your usage.
Solution 3:
Here's a list of all the versions. There is a decent discussion of the differences on Wikipedia.