Bugs item #1518269, was opened at 2006-07-06 10:11 Message generated for change (Settings changed) made by pmarcu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1518269&group_id=105970
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: extensions Group: v3.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: MKCline (mkcline) >Assigned to: pmarcu (pmarcu) Summary: XmlFile, MSXML3 XPath Support rather than XSLPattern Initial Comment: If you are attempting to use XPath Expressions and have MSXML 3.0 installed on the machine the default behaviour is for it to use XSLPattern. http://windowssdk.msdn.microsoft.com/en- us/library/ms766391.aspx There are multiple options here: a) allow for the specifying of which XML Library to use b) allow specifying the SelectionLanguage on the library (I believe from XML4 and higher this is unneccessary) c) always set the SelectionLanguage on the XmlDocument object to XPath (this might be a 'breaking change' as I don't know if there are syntax issues in XSL Pattern that wouldn't work in XPath) The documentation states that ElementPath is an XPath expression but this seems dependent on the version of XML installed. ---------------------------------------------------------------------- Comment By: tcassisi (tcassisi) Date: 2006-07-07 01:26 Message: Logged In: YES user_id=1453673 XSLPattern was deprecated some years ago and then support for it removed in later versions of MSXML. XPath should always be forcibly set on MSXML3 and below. (btw, yes, it would be a breaking change, but only if someone inadvertently was using XSL Pattern, thinking it was XPath). However, due to the change in policy regarding the "non-versioned" ProgIds, special handling is required anyway in order to take advantage of the very noticable speed increases in MSXML4 onwards. As a minimum, the logic should be: a) attempt to instantiate explicitly the MSXML4 coclass via it's (versioned) ProgId (end's in 4.0) b) if that fails, fallover to the version-independant ProgId, which would provide either v3 or v2.x. At this point, force the use of XPath via the appropriate method call. A good approach might be to allow the specification of the versioned bit, that is, the "3.0" bit to allow for future versions. This then forms the ProgId: Msxml2.DOMDocument.3.0 However, I am not away of any of the reasons to use higher versions than v4.0 for basic XML management, so perhaps the simple failover approach is adequate. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1518269&group_id=105970 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
