Unveil the difference between Web services and .Net Remoting

Web services and .Net Remoting

While many people think that web services and remoting in .net are same thing.

Attention guys both these terms differ a lot in following manners

 

.NET REMOTING	WEB SERVICES
In this programs and software components interact across application domains, processes, and machine boundaries. This helps applications to use remote resources in a networked environment.	It enables cross-platform integration by using HTTP, XML and SOAP for communication thereby enabling true business-to-business application integrations across firewalls. Because Web services rely on industry standards to expose application functionality on the Internet, they are independent of programming language, platform and device
In .NET remoting, the remote object is implemented in a class derived from System.MarshalByRefObject and MarshalByRefObject class provides the core foundation for enabling remote access of objects across application domains.	To create a Web service create a Web service class derived from the System.Web.Services.WebService class and add the methods (functionality) with the WebMethod attribute. These methods can be invoked by sending HTTP requests using SOAP.
Remote object is confined to the application domain where it is created. In .NET remoting, a client doesn't call the methods directly; instead a proxy object is used to invoke methods on the remote object. Every public method that we define in the remote object class is available to be called from clients.	You can very easily create a proxy class for your Web service using either wsdl.exe utility or the Add Web Reference option in VS.NET. The Web service proxy hides all the network and marshaling plumbing from the application code, so using the Web service looks just like using any other local object

.Net Remoting

Web Services