In this, the final part of her two part series on ADO.NET, Vaijayantee talks about the purpose of ADO.NET, scalability, XML, the ADOCommand and SQLCommand objects and more. If you're just new to .NET then Vaijayantee's ADO.NET tutorial series will have you up and running with databases in a short time.
All You Need To Know About ADO.NET: Part 2/2 - Examining the XSD (Page 5 of 6 )
As we have seen, the DataSet generated is saved as an .xsd file. If we open the xsd file in a text editor, we see the following HTML like tags, Though we need not know the XML in depth, the marked portion can easily tell us the details about our table name, column names and Key:
Passing Datasets AS ADO.NET uses XML as its default format, passing the DataSet between two applications or two components becomes very easy. To transmit an ADO RecordSet, COM marshalling has to be used while ADO.NET uses an XML stream. In general, we can say that the following are the benefits of using XML as a native data format over COM marshalling.
XML as the Native Language COM marshalling supports only a limited set of data types whereas there's no such restriction in XML format.
AS XML does not require data type conversion, it gives a distinct performance advantage over ADO, which requires data type conversion.
Firewalls are created to let HTML text pass, but to stop any system level requests from accessing the server. As XML is a text based protocol, it is able to pass through firewalls.