-
Notifications
You must be signed in to change notification settings - Fork 275
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
.NET Standard 2.0 #131
Comments
Great, I'll work on it. |
Which version of .NET Framework do you use? I don't have this problem if I set .NET 4.6 as my project's target. Probably multiple targets cause this problem? |
I'm using a new-style project (initial element is <PackageReference Include="WebSocket4Net" Version="0.15.2" /> Some of the other assemblies that the project depends on (not related to WebSocket4Net) have |
Any updates on this topic? |
Me too following the topic. |
Any updates on this? |
It is on the way: WebSocket4Net should be base on SuperSocket.WebSocket. That means server side and client side share the same protocol implementation. |
Any update on supporting Net Standard 2.0? |
Actually there is already a .net core version in NuGet: Which targets .netstandard 1.3 which is compatible with .NET Core 2.2 and .net standard 2.0. The one I mentioned base on SuperSocket.WebSocket is a complete brand new implementation. |
Net Core 2.0 and 2.2 are only compatible with Net standard 2.0. This project targets Net Standard 1.3 only, it's only compatible with Net core 1.0 Correct me if I wrong. https://docs.microsoft.com/en-us/dotnet/standard/net-standard |
I don't think so.
|
Currently, adding the WebSocket4Net NuGet package to a project running on the .NET Framework causes several System.*.dll files to be created in the output directory. These files are redundant with the similar files in the GAC. They are slower because they must be deployed, are not pre-jitted, and are not likely to be already loaded into memory by another process.
Updating the DLL and NuGet package to target .NET Standard 2.0 would avoid these problems. The package would continue to work on downlevel platforms, such as .NET 4.5, as long as no dependencies on features specific to later releases are introduced.
The text was updated successfully, but these errors were encountered: