Saxon

My question is very simple. I’m trying to read the value of an attribute of a XdmNode:

<meta xmlns="urn:dnb:stat:trafo:meta"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:dnb:stat:trafo:meta meta.xsd">
         <sectionHeader fileName="result.csv"/>
         <sectionTemplate>
                   ~

I want to get “result.csv”. I have tried using enumerators, selectors etc etc. How can this be so incredibly complicated? I’ve been working with XML via .Net for years, but cannot extract a simple attribute with Saxon Xdm-things?

Right now, what comes closest to what I would think is a solution is this:

public XdmValue GetValueFromExpression(XdmNode node, string expression)
        {
            //set the processor to use licensed edition
            var processorMeta = new Processor(true);

            //combine the path to the license file
            var filePath = Path.Combine(AppDomain.CurrentDomain.BaseDirectory, SaxonLicenseFileName);

            //Convert to URI (compatible with Java libraries)
            var fileUrl = new Uri(filePath).AbsoluteUri;

            //Set the URI
            processorMeta.SetProperty("http://saxon.sf.net/feature/licenseFileLocation", fileUrl);

            //Get the XPathCompiler
            var executable = processorMeta.NewXPathCompiler().Compile(expression);

            //Load selector
            var selector = executable.Load();

            //Set the contextitem to the node-parameter
            selector.ContextItem = node;

            //return the XdmValue
            return selector.Evaluate();
        }

The parameters passed are the xml shown above as XdmNode and the expression "//meta/sectionHeader[@fileName]".

This gives me an error though: 'Supplied node must be built using the same or a compatible Configuration'. And even after intensive googling I have no idea what to make of it, since I’m creating a new processor, compiler and selector.

For comparison: normally something like this would suffice: xml.SelectNode(“/Meta/SectionHeader”).Attributes[“fileName”];

Do the saxon DLL’s support a syntax like that?