The main idea behind incorporating XML into ASP solutions (besides vacuous fashion trends labeled "cool") is to reduce dependency on Microsoft-specific components (while simultaneously being vendor-compliant). In keeping with this realistic goal, the first Microsoft-specific target is the ADO Recordset. The second major target is the use of ASP scripting languages to render HTML.

First target: the ADO Recordset. Replace the ADO Recordset with the ADO Stream in ADO 2.5 and above:

"HOWTO: Obtain an ADO Recordset from XML" http://support.microsoft.com/support/kb/articles/Q263/2/47.ASP

"Server-Side XML in ASP” http://www.15seconds.com/Issue/990527.htm

Second target: use XML/XSL to render HTML. This is based on the Microsoft.XMLDOM object.

"Separating Content from Presentation with Server-Side XML" http://msdn.microsoft.com/library/periodic/period99/xml.htm

"'DXML': Taking a TOC from XML to DHTML" http://msdn.microsoft.com/workshop/Author/dhtml/corner042699.asp