Library tutorials & articles
XML Strengths & Weakness’ with DOM, ASP & XSL
Introduction
This article explains in a very simple manner how you can use XML in ASP and VB. Since the inception of XML people many developers have wondered why we need XML... How is it better than HTML? For starters, XML is far more powerful than HTML, and that power resides in the "X" in XML (which stands for "eXtensible"). Rather than providing a set of pre-defined tags, as in the case of HTML, XML specifies the standards with which you can define your own markup languages with their own sets of tags. XML is therefore a meta-markup language, allowing you to define an infinite number of markup languages based upon the standards defined by XML.
XML was created so that richly structured documents could be used over the web. The only viable alternatives, HTML and SGML, are not practical for this purpose. XML allows you to define all sorts of tags with all sorts of rules, such as tags representing business rules or tags representing data description or data relationships
Related articles
Related discussion
-
vb6 generated help file not working in Window 7 and Vista
by Thushan Fernando (1 replies)
-
doctype in xml using c#.net
by madarapurajesh (0 replies)
-
Like statement in Xpath
by madarapurajesh (3 replies)
-
Problem looping through xml file to play a flv video file
by Bozmeister (0 replies)
-
Creating a Windows Service in VB.NET
by davidvanr (108 replies)
Related podcasts
-
LINQ to XML
Scott's been poking around with LINQ to XML and reports his findings to Carl about life with XDocuments and XElements. They also talk about the bridge classes that link (no pun intended) System.Xml and System.Xml.Linq.
Hi
Do you have any experiences about the performance of automate generated HTML by XSL & XML
for example which one is faster:
1. seperate Asp-Sites
2. 1 Asp-Site that was generated by 1 XSL-Site (C# XslTransform)
Thanks
Schneeblitz
This thread is for discussions of XML Strengths & Weakness’ with DOM, ASP & XSL.