Geeks With Blogs
Daniel Carbajal's Weblog .NET Enterprise Development


  1. WCF is Microsoft recommended direction
  2. WCF was released on January 2006 with Go-Live Licenses, but it will be officially released on November of this year
  3. WCF is a 100% Service Oriented Architecture application development platform
  4. WCF Security Architecture is interoperable, based on WS-* specifications and it’s designed for On-Machine, Cross-Machine, and Cross-Internet scenarios.
  5. WCF Transaction Architecture is full flexible, declarative and has method level granularity
  6. WCF binary messages are smaller and faster than Remoting’s.
  7. Services versioning is better dealt with WCF than with Remoting.

.Net Remoting for .Net Framework 2.0:

  1. Remoting is not recommended by Microsoft
  2. Remoting for .Net Framework 2.0 was released in December 2005
  3. Remoting is tightly coupled Object Oriented technology and not loosely coupled Service Oriented.
  4. It has security limitations, though now it has the new secure TcpChannel
  5. With System.Transactions we can get similar transaction management capabilities but not in a declarative way



Posted on Wednesday, July 5, 2006 10:32 AM | Back to top

Comments on this post: WCF vs .NET Remoting 2.0

# re: WCF vs .NET Remoting 2.0
Requesting Gravatar...
And of course .Net Remoting doesn't have queued components!

Left by Daniel on Jul 05, 2006 11:55 AM

# re: WCF vs .NET Remoting 2.0
Requesting Gravatar...
Hi Daniel,

Very valuable information.

Thanks a lot!!!
Left by Abhijeet Rajwade on Jan 21, 2008 2:17 AM

# re: WCF vs .NET Remoting 2.0
Requesting Gravatar...
Main diffrence to me :

.NET Remoting 2.0 .. .net 2.0 +
WCF .. .net 3.5 +

Which means that WCF is useless in many cases.
Left by yo on Nov 21, 2011 4:52 AM

Your comment:
 (will show your gravatar)

Copyright © Daniel Carbajal | Powered by: