.NET Web Services: Architecture and Implementation

When it comes to building a Web service, the Web Services Description Language (WSDL) is the most popular option for describing Web services. WSDL is...

It is possible to implement Web services in a variety of ways. For example, to send a message correctly, you need to know the following: The...

At this point, you probably have a pretty good idea of what kind of information should go into WSDL. .NET and most major Web service...

One of the more difficult roadblocks to understanding WSDL is the anatomy and structure of WSDL documents. It's difficult to address the requirements mentioned in...

Following are a few rules for how I think WSDL documents should be created, with the goal of maximum interoperability without sacrificing flexibility. Here are...

It's easy to read and write WSDL documents with the .NET Framework. Specifically, the namespace System.Web.Services.Description contains a complete API for doing just that. The...

There are a couple of ways to extend WSDL beyond what the specification describes and the current state of the art. The first step is...

An idea closely related to what WSDL provides with the <binding> section and the extension elements is Web service policy. In short, a Web service...

The Web Services Description Language (WSDL) version is the de facto language for describing a Web service. It does this with a structure based on Messages...