use of RPC Client Server Architecture in c# with supporting any data Format.

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2014-07-17T20:09:00

The question makes little sense, because the old term "RPC" can be applicable to .NET only in a broad sense of this word, as very advanced and object-oriented flavors of "RPC", such as "classical" remoting or WCF. There are too many code samples on the Web, but the minimal sample will probably look bigger than you may think of.

Please see:
http://en.wikipedia.org/wiki/.NET_Remoting[^],
http://msdn.microsoft.com/en-us/library/kwdt6w2k%28v=vs.100%29.aspx[^],
http://msdn.microsoft.com/en-us/library/2e7z38xb%28v=vs.100%29.aspx[^],
http://en.wikipedia.org/wiki/Windows_Communication_Foundation[^],
http://msdn.microsoft.com/en-us/library/dd456779.aspx[^].

Believe me, even if I spend enough time to develop a minimal code sample, it would not be effective enough, because you would also have to understand it, and it would not be easy without reading on the architecture and good .NET understanding. It will take considerable time, even if you have good experience learning such things.

If you want, you can model something of the level of "RPC" using sockets, or rather TcpListener/TcpClient.

See also: http://en.wikipedia.org/wiki/Remoting[^].

—SA