Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 480069
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T00:51:20+00:00 2026-05-13T00:51:20+00:00

Mine is a general question on XML parsing practices. Lets say we have an

  • 0

Mine is a general question on XML parsing practices.

Lets say we have an XML document, and we use XPath to get some node from that document:

XMLNode node1=XMLDoc.SelectSingleNode("/SomeNode/SomeOtherNode");

Now n contains the data of SomeOtherNode. Intuitively I’d expect the following line of code:

XMLNode node2=XMLDoc.SelectSingleNode("/Child");

to populate node2 with those children of node1 which are named “Child”. But sadly it doesn’t work that way. The XPath search begins from the root of the document, not from the XMLNode object it was invoked on. Is there any way to get it to work in the “intuitive” manner? This would be convenient for a recursive or object oriented approach to parsing.

I’ve tried using the XMLPathNavigator object but it works the same way. And it seems I could set the inner text of an XMLDocumentFragment to the inner text of the given node, but that seems like an inefficient duplication of data.

Any ideas?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-13T00:51:20+00:00Added an answer on May 13, 2026 at 12:51 am
    XMLNode node2 = XMLDoc.SelectSingleNode("/Child");
    

    This will select the element called ‘Child’ from the root (/). Note that you are applying the call on XMLDoc, not on node1, so it will be relative to the root of the document. I think what you want is:

    XMLNode node2 = node1.SelectSingleNode("Child"); // edit: removed slash
    

    Which is an XPath relative to the previously selected node, not the document root.

    Alternatively, you could do:

    XMLNode node = XMLDoc.SelectSingleNode("/SomeNode/SomeOtherNode/Child")
    

    Which will select the child node directly.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.