Getting Started
  Introduction
  What is ASP.NET?
  Language Support

ASP.NET Web Forms
  Introducing Web Forms
  Working with Server Controls
  Applying Styles to Controls
  Server Control Form Validation
  Web Forms User Controls
  Data Binding Server Controls
  Server-Side Data Access
  Data Access and Customization
  Working with Business Objects
  Authoring Custom Controls
  Web Forms Controls Reference
  Web Forms Syntax Reference

ASP.NET Web Services
  Introducing Web Services
  Writing a Simple Web Service
  Web Service Type Marshalling
  Using Data in Web Services
  Using Objects and Intrinsics
  The WebService Behavior
  HTML Pattern Matching

ASP.NET Web Applications
  Application Overview
  Using the Global.asax File
  Managing Application State
  HttpHandlers and Factories

Cache Services
  Caching Overview
  Page Output Caching
  Page Fragment Caching
  Page Data Caching

Configuration
  Configuration Overview
  Configuration File Format
  Retrieving Configuration

Deployment
  Deploying Applications
  Using the Process Model
  Handling Errors

Security
  Security Overview
  Authentication & Authorization
  Windows-based Authentication
  Forms-based Authentication
  Authorizing Users and Roles
  User Account Impersonation
  Security and WebServices

Localization
  Internationalization Overview
  Setting Culture and Encoding
  Localizing ASP.NET Applications
  Working with Resource Files

Tracing
  Tracing Overview
  Trace Logging to Page Output
  Application-level Trace Logging

Debugging
  The SDK Debugger

Performance
  Performance Overview
  Performance Tuning Tips
  Measuring Performance

ASP to ASP.NET Migration
  Migration Overview
  Syntax and Semantics
  Language Compatibility
  COM Interoperability
  Transactions

Sample Applications
  A Personalized Portal
  An E-Commerce Storefront
  A Class Browser Application
  IBuySpy.com

  Get URL for this page

The WebService Behavior

Microsoft recently released a new SOAP-enabled DHTML behavior for Microsoft Internet Explorer 5.0 and later versions. The new WebService behavior enables client-side script to invoke remote methods exposed by Microsoft .NET XML Web services, or other Web servers that support the Simple Object Access Protocol (SOAP). The WebService behavior is implemented with an HTML Components (HTC) file as an attached behavior, so it can be used in Internet Explorer.

The purpose of the WebService behavior is to provide a simple way of using and leveraging SOAP, without requiring expert knowledge of its implementation. The WebService behavior supports the use of a wide variety of data types, including intrinsic SOAP data types, arrays, and Extensible Markup Language (XML) data. This flexible component enables Internet Explorer to retrieve information from XML Web services and to update a page dynamically using DHTML and script, without requiring navigation or a full page refresh.

The next generation of .NET development tools and infrastructure, including Visual Studio .NET, the .NET Framework, and the .NET Enterprise Servers, are designed for the development of applications based on the XML Web services model. The WebService behavior is particularly significant because it enables Internet Explorer to use these next-generation XML Web services.

The Microsoft Developer Network (MSDN) site provides the following documentation.

WebService Behavior Overviewhttp://msdn.microsoft.com/workshop/author/webservice/overview.asp
Using the WebService Behaviorhttp://msdn.microsoft.com/workshop/author/webservice/using.asp
The WebService Behaviorhttp://msdn.microsoft.com/workshop/author/webservice/webservice.asp

Copyright 2001 Microsoft Corporation. All rights reserved.