I have an xml file and a corresponding xsd schema for it, which validates successfully, however I'm having trouble selecting a single node. Using the following code, appData always gets NULL:
// create an XML document and validate on load
XmlDocument xmlDoc = new XmlDocument();
xmlDoc.Load(XmlReader.Crea
XmlNamespaceManager nsmgr = new XmlNamespaceManager(xmlDoc
nsmgr.AddNamespace("builda
// Retrieve general info about this wizard
XmlElement appData = (XmlElement)xmlDoc.SelectS
The XML file starts with:
<WizardData xmlns="http://buildassista
<Application name="Dev Build Assistant" version="1.00.000" />
.......
The XSD file starts with:
<xsd:schema xmlns:xsd="http://www.w3.o
xmlns="http://buildassista
xmlns:buildassistant="http
targetNamespace="http://bu
elementFormDefault="qualif
........
Can anyone tell me why I can't select a single node??
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Steelheart38,
You are correct. the select statement without the "buildassistant:" term does result in a node being successfully selected. Furthermore, I believe you are correct also about the accepted xpath usage "//<namespace>:<nodeTag>",
Thanks.
BTW, it seems that xpath queries are case sensitive as using //Application works, but //application doesn't (can anyone confirm this is correct?). However, I still can't get a 'standard' xpath query to work as described in the previous comment when I use the correct case (//buildassistant:Applicat
yes, i missed that case-sensitivity. though it was my first guess for a solution. nevertheless, good to here there's development
by standard query are you referring to //<namespace>:<node Tag>?
as i said, im not sure about this since have not explored this aspect so much yet but since it seems that you have access to the XML, retain the XSD and make the change in the XML with the foll: (it could work)
--------------------------
<buildassistant:WizardData
--------------------------
// -- instead of your existing
--------------------------
<WizardData xmlns="http://buildassista
--------------------------
maybe it will be clearer that Application node (as a child node of WizardData) belongs to buildassistant NS
Found that removing "xmlns:buildassistant="htt
Business Accounts
Answer for Membership
by: steelheart38Posted on 2005-12-05 at 05:34:52ID: 15419117
im not quite sure about this. but would there be a problem if you use the code below instead (note:without the "buildassistant:" term)?
--------------------------
SelectSingleNode("//applic
--------------------------
i don't know what effect will it be to ur expected functionality but it seems that in the XSD the default namespace <xmlns: ...> and the <xmlns:buildassistant ..> declarations refers to the same URI and could be causing the confusion as to what namespace the "application" node belongs. as i said im not sure if that's normal or not but it could be a cause
in the past i only use the "//<namespace>:<nodeTag>" (your case "//builassistant:applicati
<buildassistant:Applicatio
hope that helps somehow
steelheart38