Be Expert with us in .NET and SQL Server

  Using Web Services

•   Leverage the Web application model and the power of the ASP.NET HTTP Runtime
•   Exact type fidelity between .NET computers is not a concern and only some types of arguments can be passed

Using .NET Remoting, you can:

•   Publish or consume services in any type of application domain (ex. console, Windows, IIS, Web Service, etc.)
•   Preserve full managed-code type-system fidelity in binary formatted communications.
•   Pass objects by reference and return to a particular object in a particular application domain
• Control activation characteristics and object lifetimes directly.
•   Implement and use third-party channels or protocols to extend communication to meet your specific needs
•  Participate directly in the communication process to create the functionality you need
•   Potential performance benefits by being able to select the most optimal form of communication.

  Both ASP.NET and .NET Remoting are interprocess communication implementations. ASP.NET provides an Internet Information Services (IIS)-hosted infrastructure that handles basic types well and is familiar to Web application developers. .NET Remoting is a generic and extremely extensible interprocess communication system that you can use to create XML Web services hosted in IIS (and have all the security, scalability, and session and application state of ASP.NET and IIS), or any other type of communication

  The type of communication you need and the programming model you are familiar with are the two main criteria that should drive your choice between the two programming models.

  Using Web Services

  •Use the Web application model and the power of the ASP.NET HTTP runtime

  •Exact type fidelity between .NET computers is not a concern and only some types of arguments can be passed

  Using .NET Remoting, you can:

  •Publish or consume services in any type of application domain, whether that domain is a console application, a Windows Form, Internet Information Services (IIS), an XML Web service, or a Windows Service.

  •Preserve full managed-code type-system fidelity in binary formatted communications.  Note: XML Web services use SOAP formatting, which does not preserve all type details

  •Pass objects by reference and return to a particular object in a particular application domain

  •Control activation characteristics and object lifetimes directly.

  •Implement and use third-party channels or protocols to extend communication to meet your specific needs

•Participate directly in the communication process to create the functionality you need

•Potential performance benefits by being able to select the most optimal form of communication.