Please contact us by email.
We can provide a test release with a modified namespace of the WebSocketSharp library we use internally.

Thanks. Let us know how it goes. As I said, if needed we will help to fix this issue.

Anyway, if the plugin developers can't help, we'll make the change to the WSSharp code in our source files.

Yes, you are right. Unfortunately there's nothing we can do, because the doc is generated by a tool and we have no clue why it doesn't work.
We'll try to check again the tool options, but I don't think we will be able to solve it.

This could be something to explore: https://blogs.msdn.microsoft.com/ansonh/2006/09/27/extern-alias-walkthrough/ The problem is that we are not referencing the WebSocketSharp DLL in our API. We just included the source code in our own source code. You may ask the plugin developer to use the extern a...

That's kind of an issue. Changing all the classes to internal means we need to edit 80 files.
And in case we need to update the library in the future, we have to do it over again.
What I don't get is why a texture plugin needs WebSocketSharp.

Without waiting for the new release, we just updated the online doc. Again, thank you for reporting the issue.

You are right, we forgot to update the API doc, while we did on the other documents describing cryptography.
We will fix this in the next release. Thank you for reporting.

You should please provide more information on your setup.
Check this page please: https://www.smartfoxserver.com/support/info
No need to send your configuration for the time being, but please describe what you are doing in your code and the build target of your project.
Thank you.

Hello. It is not an issue if you redistribute our client DLLs, so don't worry. About an asset on the Asset Store containing our API only... that's not a bad idea. We will think about it. The nuget package instead is not something we released. Currently it is not something we are interested in (too m...

Hi there, I am also getting the same error, the thing is I m also using UseWebSocket.WS as I have an older version of C# client API (1.7.2) and it doesn't have binary structs (UseWebSocket.WS_BIN) . I have tried to replace it with the latest version(1.7.12) but it seem that it doesn't get fit in to...

We just released v1.7.12 of the SFS2X C# client API for Unity / .Net / Mono / Universal Windows Platform. This new version fixes a possible concurrency issue in Room, User and Buddy Variables collections. You can download the API at this url: https://www.smartfoxserver.com/download/sfs2x#p=client NO...

Jochanan wrote:Thanks

Jochanan, did you have the chance to test the updated API?

At the following URL you can download an updated version of the C# API v1.7.8.
Please try it and let us know if that fixes the issues you are experiencing.
http://www.smartfoxserver.com/temp/SFS2 ... .7.8.1.zip

sadensmol, can you please contact us by email. We may have a solution to discuss with you.
Please send an email at info AT smartfoxserver DOT com referencing this topic, thanks.