Web services are applications that combine component-based development with Web standards such as SOAP, XML, and HTTP. This site offers an ongoing series of how-to articles about Web service development on the .NET platform, as well as other articles related to Web services.
In this series, Chris Peiris shows you how to build client interfaces for Microsoft .NET Web services. You will learn how to create a Web browser, a Windows console, and WAP clients using Visual Studio.NET. All code reflects the latest changes to Beta 2.
Web services are an appealing part of the .NET Framework because they allow you to provide software to consumers as a service. Read on...
NEW:Creating HTML and Windows Clients for Web Services
Chris Peiris continues his explorations of Microsoft's Mobile Internet Toolkit capabilities with examples that consume a Web service from both a browser and a Windows client.
Creating a WAP Client for Web Services
The Microsoft Mobile Internet Toolkit contains server-side technology that enables you to deliver content to a wide variety of mobile devices. Chris Peiris shows you one simple, but real-world, WAP client you can write now that consumes a Java-based, stock-brokering Web service.
Creating a Proxy Web Service Object
By replicating a Web service's functionality on a local server, you can circumvent the security and data marshalling problems inherent in this distributed application technology. Chris Peiris shows you how to create a proxy object that acts on behalf of the original Web service.
Other .NET Web Services Articles...
Application service providers are now offering Web-hosted services for developers—a harbinger of things to come. Don Dugdale explains. (from VBPJ)
Why Web Services?
Web services extend the multi-tier paradigm enabled by Microsoft's Remote Automation and DCOM. They also open it up considerably to other platforms and operating systems. Chris Kinsman explores the advantages of this scheme by rewriting a sample from his VBITS Workshops as a Web service.
What are you using to create clients that consume XML Web Services? Are you simultaneously building WAP, HTML, and Windows clients? Are you using Java to build Web services as well as .NET? Join the discussion!
What are you using to create clients that consume XML Web Services? Are you simultaneously building WAP, HTML, and Windows clients? Are you using Java to build Web services as well as .NET? Join the discussion!