Using XPath for Your XML Based Queries in C# Programming

XPath is one of the important elements in the W3C's XSLT standard and is often referred as a query language used to help us navigate through attributes, elements and other XML objects. It helps us identify the information and process the data in xml-based data sources in an efficient manner.

The rich System.XML namespace is loaded with many helper classes that help us to fiddle with xml. XPath defines a declarative syntax that is executed by a runtime (XPath Processor) to retrieve results. The result can be a set of XML nodes or a value buried deep amidst the tags. In fact, the XPath expressions follow a hierarchical notation that explains the relationship.

Following are the basic set of expressions that one can read through to get a hold of XPATH.











XPATH Expression



To select the root node.


To select the current node.


To select the nodes from the current node


To select the parent of the current node


To match elements


To match attributes

Predicates and XPath Wildcards are the next-level of syntactical concepts that you should know. Predicates allow you to figure out specific nodes based on an expression that is present in square braces. In other words, it helps you follow the rule of exclusion to derive a result. It is often compared to an IF/Else statement.

For example, look at the following xml.

      <match result="won" score="1"/>
      <match result="won" score="2"/>
      <match result="lost" score="5"/>
      <match result="draw" score="0"/>

If you need to select the second match whose result was "won": you would write:

(//match)[@result=" won "][2] 

However, do remember that the order in which predicates are evaluated is of prime importance. The order in which they appear in an XPath expression that has a nested Predicate list, can affect your result. Each predicate follows the rule of being evaluated on the result of the immediate preceding predicate.

The next important XPath concept is the Wildcards. They are useful to select unknown xml elements.

The most widely used wildcards are the * wildcard - that matches any element node and the @* - that matches any attribute node.

An easy way to understand how these mighty expressions work is by writing more and more XPath expressions. The first reference that the developer community would recommend is the Free XPath Visualizer tool.

Also note that the examples on web, might only show you a two-node, three-element, four-attribute XML that will force you to think XML parsing is too easy. But in real life, XML is more complex and voluminous. Although XPath expressions solve every query, they have to carefully written and optimized for faster searches.

Interestingly, you may also want to know that when you work with binding sources that are XML based, you use XPath values to bind the data and not the conventional Path values.

Thanks for reading!

XPath functions

W3C Semantics

XPath Visualizer

About the Author

Srinath M S

I would love to leave a footprint in this flat world

Related Articles


  • Left Wanting More

    Posted by TexasJetter on 06/22/2011 07:39am

    This is an interesting topic, but I am left wanting more. You even admit that most examples on the web only show a two/three node XML, yours doesn't even go that far, and the XPath example is a single line. From this article I would have no clue as to how to setup and execute XPath expression. A full example would have been a great start to better explain XPath.

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Moving from an on-premises environment to Office 365 does not remove the need to plan for disruptions or reduce the business risk requirements for protecting email services. If anything, some risks increase with a move to the cloud. Read how to ease the transition every business faces if considering or already migrating to cloud email. This white paper discusses: Setting expectations when migrating to Office 365 Understanding the implications of relying solely on Exchange Online security Necessary archiving …

  • Complex hybrid environments can make it difficult to track interdependencies, increasing the risk of disrupting critical business services. In this white paper by EMA, you'll learn how application discovery and dependency mapping can help you: Meet granular targets for availability, cost, and time-to-revenue for cloud services. Accelerate mean time to repair (MTTR) while communicating better with stakeholders. Manage even the most complex hybrid environments more efficiently and effectively Understand the …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date