Talk:.NET Remoting

This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Computing: Software Low‑importance This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles Low This article has been rated as Low-importance on the project's importance scale. This article is supported by WikiProject Software. Microsoft: .NET / Windows Low‑importance This article is within the scope of WikiProject Microsoft, a collaborative effort to improve the coverage of articles relating to Microsoft on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.MicrosoftWikipedia:WikiProject MicrosoftTemplate:WikiProject MicrosoftMicrosoft articles Low This article has been rated as Low-importance on the project's importance scale. This article is supported by WikiProject .NET (assessed as Mid-importance). This article is supported by WikiProject Microsoft Windows (assessed as Low-importance).

Microsoft .NET Remoting is a key technology not particularly well explained by the relatively few books and articles dealing with it. There is an unfortunate tendency to lose track of major features among the details and alternatives. A derivative of the useful article on Component Object Model would be of help here.

Craig Bolon 14:08, 25 April 2006 (UTC)[reply]

This is advance and replacement of DCOM.The Client send an object through proxy and receive this request in server object.

In the article, it says:

The runtime itself manages the act of serialization and marshalling

I think that serialization and marshalling are synomyns.

While the functions achieved by marshalling and serialization are to a large extent similar, marshalling and serialization are different. Serialization converts the state of an object into a byte stream that can be either stored or transferred, and later deserialized into a copy with the same exact logical structure (i.e., needs the same runtime as the original object). Class definitions are not included in the serialized stream, they are loaded separately during deserialization. With marshalling, the runtimes may be different (e.g, clr and the native environment for p/invoke), and it includes codebases as well. --soum ^talk 10:29, 17 November 2007 (UTC)[reply]

I agree with Craig when he said that Remoting is not well-explained by few books dealing with it. To reinforce your learning after you read the books, I suggest you download sample codes from CodeProject. :) I'm sure it'll help you a lot. By the way, this technology is truly an amazing breakthrough in the field of networking. Jhaqr (talk) 19:14, 22 November 2007 (UTC)[reply]

I can't see a link to the topic of remoting and remoting servers and services ( such as Adobe BlazeDS ) - and it is mis-leading to have this in IPC category because of the ensuing RPC confusion

To me it would make more sense to have this an article under marshalling/unmarshalling in object serialization as a data transfer strategy - or at least to get SEE ALSO in place to avoid the impression that this is somehow uniquely a Microsoft .Net topic. —Preceding unsigned comment added by Grshiplett (talk • contribs) 19:44, 22 May 2009 (UTC)[reply]

It is now superseded by Windows Communication Foundation (WCF), which is part of the .NET Framework 3.0.

Do we have a reference for this? The same statement is made all over the web, but never (that I've seen) by an authoritative source. 65.107.60.254 (talk) 20:17, 17 August 2009 (UTC)[reply]

"...who builds distributed systems on the Microsoft platform by using remote procedure call (RPC), DCOM, COM+, Message Queuing (also known as MSMQ), .NET Framework remoting, ASP.NET Web services (ASMX), or Web Services Enhancements (WSE). Windows Communication Foundation (formerly code named "Indigo") is the strategic distributed systems technology from Microsoft that supersedes all our existing distributed systems technology stacks. Windows Communication Foundation is the foundation for effectively building next-generation distributed applications that require interoperable, secure, reliable, transacted communications." http://support.microsoft.com/?scid=kb%3Ben-us%3B907388&x=22&y=10 95.112.91.222 (talk) 22:55, 22 June 2010 (UTC)[reply]