Welcome! and rules
Joel on Software
I am really interested in and reading up on this topic and I am a bit perplexed by the lack of comment and info on this topic in this forum and elsewhere. Does anyone use it and/or have any feedback or ugly rumours about it?
I use it.
I am unclear whether .NET Remoting is inherently only possible between Windows .NET machines. I was sure this was true but then this book I am reading right now says the opposite. How would you remote to a Unix box? (I think in that scenario you'd probably be more likely to use Web Services).
I don't know. A picked-at-random Googled web page says:
"The binary messaging protocol available in the .NET Remoting framework is Microsoft's official replacement for COM/DCOM."
My understanding is that the binary *format* (i.e. binary formatter) will be replaced by another ... and that the .NET Remoting *API* will remain. Even now you can add features like encyption to your remoting, by using a custom 'channel sink'.
Indigo is pretty much a wholesale replacement of .NET Remoting. Saying that you can "add" custom encryption channel sinks is like saying that a car is a plane if you drive it into a C5 Galaxy -- in essence you might as well skip the car altogether.
Good grief... .NET Remoting is *already* passe? MS's Indigo FAQ is pretty clear that you are right. Should we start developing for Indigo or just wait for it too to go to the MS API graveyard?
A useful site, if you haven't seen it before: http://www.thinktecture.com/Resources/RemotingFAQ/default.html
For .NET Remoting scenarios requiring encryption and/or security, I've had a very good experience using it on top of IPSec.
Clay Ver Valen
Re Indigo replacing Remoting. As I understand it the situation is this:
Fog Creek Home