It's still kind of hard to edit this in the window.
It would be nice if you had a wrap function or an auto-split that would break this onto multiple lines.
3. Using your redefined prefixes, I got this to work:
/ns1:ConstituentProcessRequest/ns1:RequestDateTime
So I'm guessing you create these prefixes just for the life of the xquery? Is there a way to do something like that in .NET with xmlDoc.SelectNodes(xpath)?
I'm wondering what use this could be? I guess if was needing an XPath for XSLT, I could test it and then create a namespace in XSLT that matches the "redefined" namespace?
4. I was also hoping for something like an XPath Query Builder - maybe modeled after Microsoft's SQL Query Builder.
I also tried a simple "Books" schema with no namespaces.
I was unable to see the "Stylus Studio's Sense:X" in the Xpath Query window as I was typing. I actually read the help system and saw the example there.
5. Why isn't the right-click "Copy Xpath Query to Clipboard" feature available from the "Text" tab of an xml file (Why does the user have to be switch tree or grid mode).
6. What about Xpath V1 vs V2? Where did the option to choose go?
Subject:New XPath Query Window in Release 3 Author:Ivan Pedruzzi Date:15 Jun 2006 11:40 PM
3) The remarks on XmlNode.SelectNodes(String) reads as follow
<<"If the XPath expression requires name-space resolution, you must use the SelectNodes overload which takes an XmlNamespaceManager as its argument. The XmlNamespaceManager is used to resolve names-paces">>
Subject:New XPath Query Window in Release 3 Author:Neal Walters Date:16 Jun 2006 12:05 PM
Thanks for the info.
What about this one 4) in my original post.
I was unable to see the "Stylus Studio's Sense:X" in the Xpath Query window as I was typing. I actually read the help system and saw the example there.
I was using a simple xml documents (book/title/author), no namespaces.
Subject:New XPath Query Window in Release 3 Author:Minollo I. Date:16 Jun 2006 01:24 PM
Yes, the inability to use senseX both when no schema is associated to the document, and when the "//" operator is used, are part of future enhancements.