Make RpcLibrary more reusable

[GoogleCodeExporter]

Current implementation lacks of features and does not provide good way of 
developing them.
From my point of view it could be good
1. Move RpcLibrary into other repository specially for it.
2. Put in the same rep as Protbuf wrapper. So my WCF wrapper clone will go here 
either.
3. Make main interop stucts public and move pinvokes into NativeMethods. Is 
needed to start developing IDL generation of C# code.
4. http://code.google.com/p/csharptest-net/issues/detail?id=22
Thanks

Original issue reported on code.google.com by asd.and....@gmail.com on 24 Feb 2013 at 11:21

[GoogleCodeExporter]

Agreed this entire library has grown to a point where it is no longer 
manageable.  I'll be splitting out the projects in the near future.  I'm not 
convinced I want to join the Google Protocol Buffer wrapper.

Original comment by Grig...@gmail.com on 26 Jan 2014 at 6:43

• Changed state: Accepted

[GoogleCodeExporter]

#1. Move RpcLibrary into other repository specially for it.
Completed: https://github.com/csharptest/CSharpTest.Net.RpcLibrary

#2. Put in the same rep as Protbuf wrapper.
Will not fix: I want to keep this a 'transport' only library.  RPC wrappers 
that provide the protocol on top of the transport should be in a different 
project.

#3. Make main interop stucts public and move pinvokes into NativeMethods. Is 
needed to start developing IDL generation of C# code.
Moved to: https://github.com/csharptest/CSharpTest.Net.RpcLibrary/issues/1

Original comment by Grig...@gmail.com on 29 Jan 2015 at 5:54

• Changed state: Done