.NET provides a powerful set of classes for working with XML directly. This article provides an overview of the most important of these classes, and some examples of what you can do with them.
.NET Tools for Working with XML
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Yeah, I was a bit surprised too. I mean it’s not like .NET use XML or anything, so why would they have classes for it? Amazing!
I am just begnning to write programs using c# and XML. This short article was quite useful.
I think I’ll stick with <a href=”http://www.xmlsoft.org“>libxml2. I won’t have to worry about MS taking their technology and driving it into a proprietary ditch or pulling it out from under us like they’ve done so often.
Unfortunately, the .net XML controls all suck. You can have perfectly valid XML with valid XSD’s and it still won’t work properly.
You have to conform to what MS defines as valid XML. >:(
Unfortunately, the .net XML controls all suck. You can have perfectly valid XML with valid XSD’s and it still won’t work properly.
You have to conform to what MS defines as valid XML. >:(
Do you have any examples to back that up?
I didn’t see anything about XmlSerializer and xsd.exe. IMHO that is only way to fly when working with large xml documents.
>What’s up with all the .NET promotion work on OSnews? … NET isn’t really all that special, if you think of it
Well, if we use your same agruement than OSNews should then not report on: Mono, Mozilla, Java, XFree86/X11 but OSNews does and in my opinion should. Just because you might not be interested in a particular article doesn’t mean other’s are not.
Keep up the good work Eugenia!
Maybe MS has decided they want to be part of the worldwide software community. Maybe they have decided that 15% of the worlds software business 15 years from now would be all right. Who knows? I pray they will decide that they want to work with others for the betterment of our world. Time will tell.
The articles neglects to mention that the MSXML4 parser (COM+) is a whole lot faster (between 5 and 20 times depding on the size of the document) than the current .NET (v1.1) XML Classes.
MS has acknowledged this, and has said that V2 will be “at least as fast” as MSXML4.
So if you’re doing anything serious with XML in .NET ath the moment, your only real option is to use Interop and the old parser.
Using the new XML parser works very well with .NET
“the .NET Framework provides you with tools that are not only powerful but easy to use.”
I had to laugh when i read this and then saw a basic example which took the better part of a page. Here is a piece of mathematica code that does the same thing in 243 characters what takes 1328 characters in the easy to use .Net
With[{symbolicxmlexp = Import[“checkbook.xml”][[2, 3]]}, Total@Cases[Select[symbolicxmlexp, MemberQ[#[[3]],
XMLElement[“category”, {}, {“groceries”}]] &], XMLElement[“amount”, {}, {
theamount_}] -> ToExpression@theamount, Infinity]]