-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do you have an update plan available on .net core? #38
Comments
+1. |
I think there is no simple and really cool option like this in .net core. |
@NeedJustWord has sent PR. Anyone wants to test it? I will merge if it works properly. |
I'm going to take some time to try. |
Hi Halil, I have been using your SCS as TCP Server for a long while within standard .Net framework. And now, I have to move on .Net Core. I still want to use SCS. At a glance, I noticed that ASPNet Core doesn't have "System.Runtime.Remoting.Proxies and System.Runtime.Remoting.Messaging" anymore. It complains that accordingly. Long story short question, by chance do you have .NET Core version of SCS? Or a suggestion for a solution or an alternative one it does as good as you developed SCS? Hoscakal, |
Hi, I definitely want to do this, but I don't have time currently. I would probably use the Castle DynamicProxy instead of Remoting.Proxies. I don't know a good alternative. You may want to try signalr. But I love SCS since it is very simple to use, fast & stable. |
Thanks a lot for your reply, it is clear, understood. I would also love to contribute that but my main focus on the IoT devices recently. Therefore, until you have .Net Core version, I am going to try out "NetCoreServer" and see how they cope with the features you have. Thanks a lot again for the SCS anyway. It still works and it will work on my applications in some industries all over the world without a single hiccup. |
No description provided.
The text was updated successfully, but these errors were encountered: