Kerry Jiang

Memory leak. There is no enough memory for the client. The problem may not be caused by SuperSocket.ClientEngine.

Please don't use that batch file to build. It is used for creating nuget package.

Ok, I made an enhancement to expose the socket object. https://github.com/kerryjiang/SuperSocket.ClientEngine/commit/4f386ef4e5dcf8f6c7a6eb537b575987424a1da5

Of course, Yes. But you need do it by yourself. Define your command interface and commands, and then dispatch packages to commands,

Probably yes, it can be shared between server side and client side.

Sorry, could you provide more information about this problem?

Do you mean the Close event of EasyClient doesn't work?

using the namespace SuperSocket.ProtoBase. The usage is similar with the receive filters of SuperSocket: http://docs.supersocket.net/v1-6/en-US/The-Built-in-Common-Format-Protocol-Implementation-Templates

run the following command to restore the reference from NuGet: nugget restore xxx.sln

You can use any version of it including .NET 3.5+ or .netstandard version.