Add support for dynamic proxies with non-public interfaces

[LiangJy123]

Hi~

I got a exception that "Attempting to implement an inaccessible interface"
when running this line:

       var RpcClient = JsonRpc.Attach<IRPCFuntions>(stream);

the IRPCFuntions is defined as follows

         interface IRPCFuntions
        {
             Task<int> SumOfAsync(int a, int b);
             Task<int> DifferenceAsync(int a, int b);
        }

I spent half a day but didn't find what caused the exception, can you help me ?

[AArnott]

Make the interface public.

This is something we could enhance to remove the requirement though, so I'll keep the issue active.

[LiangJy123]

Thank you very much!
I used to try to add "public" but the "IRPCFuntions" was defined in the class ,so it didn't work.
After got your tips, I try to define them out of the class and add "public" , it runs successfully.

[AArnott]

Reopening to track ability to implement internal interfaces.

[AArnott]

vs-mef does this already (with 95% feature complete).
We should try to consolidate the implementation into a reusable package so that this can be shared between vs-mef, vs-streamjsonrpc and even messagepack.

[AArnott]

messagepack issue tracking it: MessagePack-CSharp/MessagePack-CSharp#88

[peterwald]

+1 for this feature, to support implementing an RPC protocol without publicly exposing all of the interfaces/types involved.

[AArnott]

@peterwald: giving a thumbs up on the issue description is a great way to accumulate votes.