.Net Remoting Vs Web Services

[Jagdish Gada]

Hello, If anyone know the difference between the .Net Remoting and Web services then please provide me that. I have search about this on internet but the concept of the .NET remoting is quiet complicated and that is why I am not able to get it properly. So, if you know it then tell me that with proper explanation.

[Praetor]

When the .NET and the .NET Framework developed by the Microsoft he introduced the some of the new technologies which are based on the web services and .NET remoting. If you are preparing the distributed application then you can make use of the .NET remoting for getting powerful framework. If you want to use it then first of all you need to check both of the technologies and then from that you can decide which is better in both. As we know the Web services technology uses the HTML, xml, and soap for making connection and communication it can perform the different platform working. Remoting can able to take advantage of remote resources in a networked environment.

[Katty]

For .Net remoting you can make use of the code below:

using System;
namespace RemoteClassLib
{
   public class Test : System.MarshalByRefObject
   {
      public Test()
      {
         Console.WriteLine("This is a constructor");
      }

      public string Tryed(string name)
      {
         Console.WriteLine("Tryed  called");
         return "Constructor " + name;
      }
   }
}

[kelfro]

Web services and .Net remoting are having following different features:
ASP.NET Web Services :

• You can access this only over HTTP
• It work in stateless environment
• It will support the datatypes which are defined in the XSD type system.
• Ir will support interoperability across platforms.
• These are reliable.
• It provides you the extensibility.
• It is simple.

.NET Remoting :

• You can access over any protocol.
• It can provide support for both stateful and stateless environments.
• It can take advantage of IIS for fault isolation.
• It is more extensible and also allow the components of the .NET remoting framework.
• But it is quiet Complex.

[Zecho]

I think you must need to read the books to get the solution :

• Programming Microsoft ASP.NET 2.0 Core Reference by Dino Esposito
• Essential ASP.NET 2.0 by Fritz Onion, Keith Brown
• Pro ASP.NET 3.5 in C# 2008, Second Edition by Matthew MacDonald
• Programming ASP.NET by Jesse Liberty, Dan Hurwitz
• Murach's ASP.NET 2.0 Web Programming with C# 2005 by Joel Murach, Anne Boehm
• Beginning Object-Oriented ASP.NET 2.0 with VB .NET by Brian Myers
• ASP.Net 2.0 Web Parts in Action: Building Dynamic Web Portals by Darren Neimke
• ASP.NET AJAX Programming Tricks by Matthew David Ellis

[Reegan]

If you take look at the book of Microsoft .NET Distributed Applications: Integrating XML Web Services and .NET Remoting then you will able to get the following differences between the XML Web service and .NET Remoting technologies:

• XML Web services are more restricted than objects exposed over .NET Remoting. An XML Web service works in a similar way to a SingleCall .NET Remoting object. It isn't possible to create a singleton or a client-activated object.
• Because of the restricted nature of XML Web services, the design issues are simplified. XML Web services are generally easier to create than remotable components (and easier to design well).
• Communication with .NET Remoting can be faster than XML Web service communication if you use a binary formatter. XML Web services support only SOAP message formatting, which uses larger XML text messages.
• XML Web services support open standards that target cross-platform use. For example, each .NET XML Web service has an associated WSDL document that describes how a client can interact with the service. Therefore, any client that can parse an XML message and connect over an HTTP channel can use an XML Web service, even if the client is written in Java and hosted on a UNIX computer.
• XML Web services are designed for use between companies and organizations. They can use a dynamic discovery mechanism or a UDDI registry that "advertises" services to interested parties over the Internet.
• XML Web services don't require a dedicated hosting program because they are always hosted by ASP.NET. That also means that they gain access to some impressive platform services, including data caching, Web farm-ready session state management, authentication, and an application collection for global, shareable objects. These features, if required, can be extremely difficult to re-create by hand in a component exposed through .NET Remoting.
• Because XML Web services work through Microsoft Internet Information Services (IIS) and ASP.NET, they can communicate with clients using the default HTTP channel (usually port 80). This means that consumers can use XML Web services just as easily as they can download HTML pages from the Internet. There's no need for an administrator to open additional ports on a firewall.