There have been several articles on 4Guys on retrieving XML from an ADO Recordset. Scott Mitchell's article Creating a Function to Stream a Recordset to XML examined how to use the MSXML COM components to convert a Recordset into an XML string. David O'Neill extended Scott's article in Increasing ConvertRStoXML() Performance and, in Simplifying ConvertRStoXML() and Transforming With XSL, looked at how to simplify the entire process by using an XSL stylesheet.

XML 1.1 is fairly controversial: it just adds some niche features that most people don't need. We recently added some XML 1.1 support to Topologi's XML editor; I was surprised by how straightforward it was, but also perhaps premature.

The .NET Framework has built-in support for XML processing. Discover how to use XML in .NET and what these benefits can do for you.

Nowadays XML is the de facto standard for exchanging data between different systems and platforms, so providing a mechanism that allows us to import XML is very useful. In this case study, Giuseppe Naccarato will be using the XmlReader object and reflection to build a powerful general-purpose component for mapping XML to C# objects.

Taking advantage of both the new set of classes introduced by .NET to manage XML and SQL Server 2000 XML features, Carlos Walzer will explain how to create a generic aspx page to add reporting capabilities to an ASP.NET site. This reporting aspx page is the result of combining System.Xml.XmlTextReader, XSLT, streams, and stored procedures that return XML using the FOR XML clause.

Sarvega™, Inc., the leading provider of high-performance XML networking solutions, announced today the integration of its XML Guardian™ Gateway with Web Services Distributed Management (WSDM) from Computer Associates International, Inc. (CA), providing customers a comprehensive solution for processing, securing and managing XML-based Web Services. Using CA’s new WSDM 3.1 Observer Development Kit (ODK), integration between the two products will deliver native Web services management capabilities from within the XML Guardian Gateway.

Learn the difference between typed datasets and classes generated by the xsd.exe tool, as well as how to extend this code generation process by reusing the infrastructure classes supporting it, while remaining compatible with the XmlSerializer.

.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.

This sample shows how you can obtain a Dataset from (in this case) a SQL Server database, and then write it out to an XML Document. As an "Extra Added Bonus(tm)", it can show you how to write the schema as well. The SQL Server database in question is the venerable and useful Northwind database.

There is always been a need that there will be an intelligent middle Layer between Database Server and the UI Code. There are many ways but one fantastic approach came in picture with the XML. There are rich classes in System.XML which make it pretty simple and effective. Here i had made a similar application where I am solving two purpose. One thing is still the things has not come as Code Behind Approach in case of Mobile Forms and whatever till now we had done is not recognized under that approach.

.NET Beta 2 was released yesterday at tech-ed, 2001, Atlanta. Many things have been changed in Beta 2 since Beta 1. In this article, I'll cover changes in XmlNavigator class replaced with XPathNavigator.

I have developed a C# component that converts objects to an XML stream and vice versa. The main .NET focus is on System, System.Reflection and System.XML assemblies. The user has access to a default constructor and four public methods; two methods to create an XML stream or file from an object and two that creates an object from from an XML file or stream

Here is something really wonderful in Mobile field .This example is for authenticating the Mobile Users against his settings stored in XML file. This is really good where all the ease of XML is applied. Function open the XML file and particular node data validate it against user inputs and do the specified.

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.