NET framework takes care of the XML and SOAP for us and we will allow it to do so without examination. What you will not see is a lot of XML and SOAP. The best part about Web Services is that XML and SOAP do their bit behind the scenes all you have to do is write the code. NET objects to and from XML and pushing them back and forth across networks. The SOAP protocol is capable of marshalling. More importantly XML is an extensible, self-describing markup language, which means you can use XML to describe objects that haven’t even been invented yet.

You already know that text can be sent across the Internet. XML, or Extensible Markup Language, is basically text. The reason Web Services are different is that Web Services are based on reliable, simple, open standards-based technologies, specifically XML and SOAP. Unfortunately, DCOM is based on a proprietary standard. Until recently you used DCOM to interact with high-level objects across process boundaries. It just happens that the Internet is the most important environment that Web Services target.

Of course, you don’t have to use Web Services with the Internet you can use Web Services within the same application or across any other network. Web Services is a way of marshalling procedure calls across the Internet.

Visual basic net using