Remoting is Dead?

Vikram,

Thanks so much for the info. Do you know if Indigo will be available for the Compact Framework as well? That would be sweet!

--Adam

Adam- this is a valid question and one unfortunately that I do not have the answer to- however, I am hoping that you are periodically checking this for replies. I have sinced phoned your parents to let you know I am searching for you. For some strange reason you have been on my mind and am wondering how you are faring-

I'm in Manhattan, singing of course, and having a wonderful time. Been here since I finished college- have been to Europe singing- am hopefully heading to Asia for 6 months, and have been in the recording studio.

My hope is that you are well and that life has blessed you.
Feel free to give me a ring or drop me a line at tonidolce@hotmail.com/ 646.734.6852 -

All my best,
Toni

Perhaps why Remoting is dead is because there are not little wizards to guide people through the act of setting it up. From the way that I interpret the technology and Microsoft's pushing of it is, "it's there. this is what it does and now lets move onto wonderful web services and what we can do and web services are so wonderful."

I have also heard horror stories of poor performance or major memory leaks when passing certain data related objects over remoting channels.

I personally am extremely hesitant to use remoting technologies in place of situations where we currently use Web services but would like to be able to leverage the power of remoting due to alot of the horror stories that I have heard.
Perhaps if MS spent 1/20th the time and resources that they spent on web services which overall are extremely simple as all they facilitate is the transfer of data while Remoting which is alot more complex and imho should receive much more time, resources and developer attention then perhaps people would not be left with such a negative impression on .NET Remoting.