It attempts to find 6 first, then 5, then 4; if none is found, the program should say that MSXML 4.0 is required (AFAIK xsd validation was not fully implemented until 4).
I haven't worked much on my MSXML automation code recently because I want to switch to Xerces-C. On Linux the program already uses Xerces-C (so the source is all there), but so far I haven't found a version that will work with a free compiler on Windows.
More importantly, is validation working as it should on your system? If it doesn't, please let me know and I will look into this in more detail.
-Gerald
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, it seems to be working fine. Can't tell whether it's using MSXML6 or MSXML4.
I'm having trouble with <xsl:key> and I don't know where the issue is. I'm trying to make a key using non-Latin1 characters, which doesn't seem to work anywhere I've tried it. I figured MSXML6 had a better chance of having this, in case it is a matter of selective implementation.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If MSXML6 is installed on your computer, I'd expect it to be the one that's used. The automation calls 6, 5, 4 one after the other; the first one that's found is used.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On the Windows side, are you using MSXML 4 or 6? Is that changeable by the user (or desireable to be changeable)?
Thanks,
Roger Sperberg
It attempts to find 6 first, then 5, then 4; if none is found, the program should say that MSXML 4.0 is required (AFAIK xsd validation was not fully implemented until 4).
I haven't worked much on my MSXML automation code recently because I want to switch to Xerces-C. On Linux the program already uses Xerces-C (so the source is all there), but so far I haven't found a version that will work with a free compiler on Windows.
More importantly, is validation working as it should on your system? If it doesn't, please let me know and I will look into this in more detail.
-Gerald
Yes, it seems to be working fine. Can't tell whether it's using MSXML6 or MSXML4.
I'm having trouble with <xsl:key> and I don't know where the issue is. I'm trying to make a key using non-Latin1 characters, which doesn't seem to work anywhere I've tried it. I figured MSXML6 had a better chance of having this, in case it is a matter of selective implementation.
If MSXML6 is installed on your computer, I'd expect it to be the one that's used. The automation calls 6, 5, 4 one after the other; the first one that's found is used.