views:

837

answers:

4

We have been using GenuineChannels in our product for the last 4 years. GenuineChannels now appears to have become unsupported and the main developer guy Dmitri has I think joined Microsoft. I have the source as part of the product but not the networking / .net knowledge to support it.

Has anyone found a good alternative to GenuineChannels for good .net remoting? I need our software product to run on top of some supported software!

+1  A: 

WCF (Windows Communication Foundation) is the way to go - much more scalable, easily swappable to other technologies (if you need in the future), and builtin to .NET 3.0.
A lot of other nice stuff there, too... http://msdn.microsoft.com/en-us/netframework/aa663324.aspx

AviD
+1  A: 

WCF, Windows Communication Foundation is the approach you should look into. WCF integrates web services, .net remoting, distributed transactions and message queuing into a common communications model.

Getting started with WCF is at http://msdn.microsoft.com/en-us/library/ms734712.aspx

The tutorial is at http://msdn.microsoft.com/en-us/library/ms734712.aspx

Oreilly has a book about WCF: http://oreilly.com/catalog/9780596526993/

dsacks
+1  A: 

Does anyone know of an alternative that doesn't involve WCF? WCF requires the newer version of the .NET framework, but GenuineChannels works even with version 1.1

+1  A: 

There is a product called DotNetRemoting that claims to be an easy replacement for GenuineChannels. They even have a section of their forum dedicated to converting from GenuineChannles to DNR.

adrianbanks