A Straightforward Explanation of XML And Visual Basic


T

taj sha

Xpath is easily the most popular choice for XSLT users when attempting to pick nodes with an xmltree. This ability to pull nodes from an XML DOM is the reason that parsers are so popular, the MSXML parser can carry out Xpath queries which enable it to reference any nodes inside of an xmltree making use of quite intricate queries.

XML is hierarchical by nature and therefore whilst it would appear easy enough to populate and represent XML as a tree, this is not always the case inreality you may not need to achieve this, as an example you could prefer to bypass some braches or nodes.

In actual fact, you might simply want to build a treeview structure that displays simply the most relevant nodes, you might additionally wish to be able to pick the nodes, causing more detailed information to appear in the right hand pane of your application. This is usual for most Explorer-type applications.

The best way where you can achieve this could be to code the required performance that will show your XML, straight to your program.

Having said that this isn’t ideal and may actually cost time and effort when you have to recompile your application each time you wish to affect thedisplay, worst still it means fooling with loads of unpleasant DOM code.

The best choice would be to move the layout instructions to an XSLT stylesheet which can then style the xml data into a format suited to processing.

However feel free to use any of the well-known xml vb parsers or if you'll want to generate code from your XML, try <a href="http://www.liquid-technologies.com/xmldatabinding/xml-schema-to-vb.aspx">Liquid XML Visual Basic</a> to generate your VB code automatically.
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top