A few months ago Mark Fussell wrote an article entitled What's New in System.Xml for Visual Studio 2005 and the .NET Framework 2.0 Release. Mark Ihimoyan has a followup series of blog posts which mentions which of the new features of System.Xml mentioned in Mark's article will actually be in the .NET Compact Framework.

Excel XP has a cool feature related to XML as the product can easily read and write properly-structured XML documents, run web queries against properly-structured XML data sources and save entire workbooks as XML spreadsheets. This article demonstrates one view to the utilization of this feature in .NET, namely creating a basic spreadsheet that has formulas.

This part takes a look at the role that XML data plays in .NET and how we can use XML data as a datasource.

One of the biggest differences between DataSet and the old Recordset is that data in ADO.NET is transported in XML format. That makes it a structured text document that can be read by anyone on any platform. This makes DataSet "interoperable" between a lot of computers - Microsoft and non-Microsoft since XML is an international and vendor neutral standard. After you create an XML document using methods provided by DataSet, you can parse it in .NET programmatically using the System.Xml.XmlDocument object.

Based on a real-world project, this article shows how to handle XML data in .NET using C# DataSets and DataViews. The article presents, step by step, how to bind, read, and view XML data and generate graphical reports with the built-in Crystal Reports engine. The article puts special emphasis on XML standardization and interoperability issues experienced during the project, and presents workarounds for existing limitations.

The container.DataItem is an easy-to-use method to bind XML to a control. You can use a repeater, list control, or any other control to bind the XML. If you have have worked with XML and a repeater control, you know what I am talking about. In this short "how to," I will show you how you can bind a nested XML element to a repeater control. But, first of all, let's see an example where we bind a simple XML to a repeater control.

The C# compiler is able to extract XML comments from C# source files. If at compile time, the /doc command-line option (or the equivalent option in the Visual Studio® .NET IDE) is used to specify a target documentation file, all of the comments are extracted from the source files and are written in an XML format to the target file. Visual Studio .NET can then use this file to display IntelliSense® when the XML file is in the same directory as the compiled assembly (the documentation file must also be named the same as the assembly, with a .xml extension). Both the Visual C++® and Visual Basic® compilers will support this feature in Visual Studio 2005.

This article is a companion to Code Generation in the .NET Framework Using XML Schema article published in the MSDN XML DevCenter. In that article, I introduce you to the main classes in the .NET framework that enable code generation from XSD files, the very clases the XSD.EXE tool uses. The ideas come from my initial post on Customizing XSD->Classes code generation, the "easy" way. In this article I'll create a VS.NET custom tool for the code shown in the MSDN article.

As you may have guessed from looking at the top of this page, the House of COM column that appeared in the May 2001 issue was my last column on COM (I have already started the bidding war on eBay for that soon-to-be-collector's edition). Dedicated readers may have noticed that I haven't been using the column to write about COM per se for some time. Rather, for the past three years, my work has been shifting to encompass other software integration/component technologies, such as the Common Language Runtime (CLR), ISAPI, XML, SOAP, and Web Services.

The schema library in Word 2003 is where so much is happening for developers. While some end-users will venture into the schema library, most should not care what is in there. A well-architected Word XML solution should keep the inner-workings tidy and transparent.

This course is best suited for individuals with a good understanding of XML and the supporting technologies like DOM, XSLT, and XML Schemas.

The XML support in .NET is provided via five namespaces, System.Xml, System.Xml.XPath, System.Xml.Xsl, System.Xml.Schema, and System.Xml.Serialization. These namespaces are part of the System.Xml.dll assembly. The classes in these namespaces are designed to support XML 1.0, XML Namespaces, XPath, XSLT, DOM, and XSD Schema W3C standards. The .NET Framework does not support SAX, instead supports a different, "pull" based streaming API.

XML is pervasive in .NET. In order to pass the MCAD/MCSD Exam(70-320): Developing XML Web Services and Server Components with Visual C# .NET and the .NET Framework, you need to know XML, starting with this section on accessing and manipulating XML data.

SOAP technologies usually exchange XML over HTTP, but SOAP has its pros and cons, and a lot of discussion has focused on how to use XML more directly to communicate between applications. This tip describes the direct approach, and discusses where it is most appropriate. It also discusses how to use WSDL to describe such services.

A settings class that can be used to store values in an XML document.