WCF (Indigo)

WCF (Indigo)

• Tarek Haoula

  Greg, we haven't deprecated .NET Remoting; in fact, we just added a slew of new features to Remoting [1] with the .NET Framework 2.0. WCF is the next version of Remoting [2]. So if you're starting a new project, you'll probably want to use WCF from the start.

  Cheers,

  JJustice [MSFT]

  [1] http://blogs.msdn.com/manishg/archive/2005/12/02/499629.aspx

  [2] http://blogs.msdn.com/richardt/archive/2004/03/05/84771.aspx

  
  

• jjbunn

  There is no migration path from .Net remoting to WCF.

  Try to see it this way:

  If you could re-implement your current remoting functionality, what technology would you use Webservices/WCF or .Net remoting

  If the answer is .Net remoting just upgrade to Framework 2.0 (get some nice extra features).

  If the answer is Webservices, take a good look at your current functionality and reimplement it with WCF.

  Sandor

  
  

• Bene

  my worry is depreceation.

  alot of things that one would have used remoting for before; one would now use WCF.

  
  

• evilone

  Greg, since WCF is now available as a "Go Live" release, our guidance is evolving to recommend WCF for almost all scenarios. I might still use Remoting for a heavily cross app-domain app, but in all other cases I'd use WCF. WCF has much better custom protocol support, performance, and interoperability, as well as significant feature additions like transactions, strong manageability support, reliable sessions, and MSMQ integration.

  Cheers,

  JJustice [MSFT]

  
  

• Change2

  Hi Greg, glad the information was useful to you. You asked about how we handle "notification" style messaging in WCF. To do this, use a callback contract [1] with a duplex channel. This will let you make a call to the service, and then let the service initiate communication back to the client when it comes time to send a notification.

  Hope that helps,

  JJustice [MSFT]

  [1] http://windowssdk.msdn.microsoft.com/library/en-us/WCF_con/html/500a75b6-998a-47d5-8e3b-24e3aba2a434.asp

  
  

• Hiryux

  Thanks J Justice

  Just another quickie.

  In researching WCF I happenned accross one major piece of functionality that seemed to be "missing" (deliberately but I use it quite a bit). The missing piece is asynchronous notifications and I assume this is involved the move towards a more SOA based environment.

  I could quite easily use a delta based polling mechanism but would prefer to avoid such things. The second work around would be to move into a peer environment but this is also unacceptable for my uses as there are often times firewalls in between (in fact I can not use the default remoting channels as they also implement a secondary socket). Is there a way to work around this little tid bit in WCF

  Greg

  
  

• Thomas Ott

  just posting this for the googlers who come accross this for new development ...

  “So, should I continue to use remoting in my applications today “

  Remoting as a technology has some useful capabilities in niche areas. In particular:

  • Use .NET Remoting for calling between components hosted in different app-domains inside the same process
  • Use .NET Remoting for handling custom wire protocols and formats.

  However, we recommend minimizing your use of .NET Remoting to these niche areas, and suggest that you utilize Enterprise Services for the development of components inside your services, and ASMX/WSE for exposing your services at your boundaries. This will help you develop Service Oriented systems today that migrate to Indigo as smoothly as possible in the future.

  
  
• WCF (Indigo)