MS Dumps .NET Remoting

Yes, it is final, MS is dropping .NET Remoting support. Funny. COM+, DCOM, and MSMQ will be supported by Indigo, but .NET Remoting WILL NOT. More info in this video.

6 Comments

  • You're getting a bit ahead of yourself!



    Remoting is still there, what is dropped is the Context model and the channel sinks in remoting, not remoting as an activation model! You should fear Ingo and Indigo if you shall say Remoting is dead!

  • Just got out of the Don Box Indigo overview. .Net Remoting is still breathing and will be supported.

  • Guys, I've just been out on dinner with the Indigo folks. Remoting will be around as long as something even better reaches your desks. MS never dropped support for some technology which has been used by hundreds, if not thousands of applications.



    -Ingo

  • “we have no plans to interop with .NET remoting or older versions of WSE"



    -- Joe Long (PUM XML Enterprise Services)



    So, yes, you can use remoting all you want, but it won't "interop" with Indigo. I'm interesting in what the distinction is here. How broken will your remoting apps be when Indigo comes along? Fortunately, we use WSE, not remoting here. :-).

  • You guys get it all wrong, as it looks.



    In the context of indigo:



    * Remoting is dead and not ineroperating

    * Web services are DEAD AND NOT INTEROPERATING.



    Yes, right.



    Indigo is it's own infrastructure. It uses WebServices below (WSE i na new edition) and it can also handle remote objects.



    What you THEN dont have is apart of the remoting stack - Indigo has its own stack. And they dump the ContextBoundObject.



    Good or bad? I dontknow - I dont care. It looks like our EntityBroker is on the track to integration since yesterday :-) Nice.



    But one thing it does not mean: remoting is far from dead, and where Indigo brings it's own web service infrastructure, it also handles remote business objects.



    Nice.

  • API != Plumbing. Plumbing will be broken for everything (Except ES with DCOM). API will stay with very minor changes (mainly drop of transparent proxy by new keyword and switch from ContextBoundObject to a CallContext which makes a whole lot of sense).



    Saying remoting is dropped is not true, but there's no plan to interoperate with the binary channel sink. And migrating will be very easy. So i insist in saying, remoting is not dead. It's even less dead than it seems that Indigo will ship separately from .net 2.0

Comments have been disabled for this content.