Indigo != Remoting; Remoting != future
Just saw a post here by Jesse Ezell that states that MS will be dropping remoting support.
Quote: Yes, it is final, MS is dropping .NET Remoting support.
and this is further underlined by a post here by Drew Marsh covering Don Box's presentation that states
.NET Remoting is awesome, infinitely extensible, but not the future. It will be supported for a long time, but the future, as Microsoft sees it, is more along the lines of what ASMX provides today.
so while remoting isn't going to be immediately dropped, its future is limited, although an approximate time limit is unclear. I like remoting and have used it extensively in many systems I have designed but it looks like this inclination of mine needs to be changed to be inline with future direction. I am sure a viable migration path will be provided my Microsoft as we move forward, I just hope its a nice warm fuzzy one ;-)
The message is clear though. To design for the future, dont use anything too remoting specific, or at least make it flexible enough to support a service-oriented design/architecture when required, to eliminate/minimise rework in the future. I guess a very general way to look at it is, “How easy can I make this remoting call/conversation a web service(s)?“.
Looking forward to more PDC posts.....