Wow! You're too fast! Right after I wrote my post and the page refreshed to show the full thread, I noticed that you said that you already changed the version number so I never should have made that post.
But I was hurrying off to work and didn't have time to edit it.
I just bought a shiny, new laptop with Windows 7 installed so I can actually try to test/resolve this issue... tonight.
I have some scripts that I can use to drive this process and test it outside of Awasu and I think
"Can we support both? MSXML6 is pre-installed on Vista and later, so go for that first and if it fails, try MSXML4."
Yes I can loop through an array of ProgIDs and attempt to instantiate V6, if that fails attempt to instantiate v5, etc.
There's also a default version of MSXML that you can instantiate with the ProgID of "Msxml2.XMLHTTP".
You can check the value of this registry key to find out which version is the default:
I did look at my Windows 7 laptop at home this morning and it looks like, as with previous editions of Windows, version 3 is the default. I think the simple HTTP call that make should work with version 3 to.Error logging
"Instead of logging to the event log, couldn't we insert the error message into the output?"
). But that's a good idea I could add an error message that would invalidate the XML, I'll have to try that.Reference material
Also the MSXML SDK
(third downloadable MSI file
) contains information regarding embedding script within XSLT.