Analysis of ASP. NET Web Services

The basic structure of ASP. NET Web Services provides simple APIs for Web Services by ing SOAP messages to method calls. This mechanism is implemented by providing a very simple programming model based on ing SOAP message exchanges to method calls. Clients of ASP. NET Web services do not need to understand the platform, object model, or programming language used to create them. Services do not need to know the clients that send messages to them. The only requirement is that both parties should recognize the SOAP message format being created and used, which is composed of the WSDL and XML architecture (XSD) web Service Contract definition.

. NET Remoting provides a basic structure for distributed objects. It uses flexible and scalable pipelines to provide full object semantics of. NET to remote processes. ASP. NET Web Service provides a very simple programming model based on message transmission. NET Remoting provides complex functions, including passing objects, callbacks, and multi-object activation and lifecycle management policies through values or references. To use. NET Remoting, the client needs to understand all the details. In short, you need to use. NET to create a client .. The NET Remoting pipeline also supports SOAP messages, but note that this does not change the client requirements. If the Remoting endpoint provides. NET-specific object semantics, the client must understand them whether or not they are using SOAP.

The simplest example of Remoting is remote object:

Create a class library project: RemoteObject

 
 

  
  
using System;  
  
  
namespace RemoteObject  
  
  
{  
  
  
public class MyObject:MarshalByRefObject  
  
  
{  
  
  
public int Add(int a,int b)  
  
  
{  
  
  
return a+b;  
  
  
}  
  
  
}  
  
  
} 
 
 

1. DataList and Repeater controls of ASP. NET
2. Analysis of IIS ing in ASP. NET
3. Overview ASP. NET status types
4. Introduction to ASP. NET and Web servers
5. EnableViewState attribute of ASP. NET