Please make a version for .net Core 2.0

[kooboo-binbin]

Please make a version for .net Core 2.0

[imaji]

Hi,

Yes, we're just looking at timescales to make a .net standard compliant version.

I haven't got a date for you yet though.

Best regards,
John

[nicolasguzca]

Hi John, any updates on the .net Core 2.0 version?

[justin-lavelle]

I have a fork for netstandard2.0 https://github.com/justin-lavelle/pusher-websocket-dotnet-netstandard
It's also on nuget PusherClient.NetStandard

[Misiu]

@justin-lavelle could You make a PR with all the changes?

[imaji]

I've got a version we're going to merge in shortly that adds in support for .net standard 1.6 & 2.0

[Misiu]

@imaji awesome news 😄

[bddckr]

Will the Standard compliant version still include WebSocket4Net or is System.Net.WebSockets.ClientWebSocket enough?

I'm having a hard time figuring out whether it supports the same OS/device combinations besides being part of .NET Standard 2.0 and whether that's an issue for this library.

[Misiu]

@imaji any updates?

[Misiu]

ping

[kn100]

Hi @Misiu - I will also bring this up in our next standup and keep you up to date on our plans.

[Misiu]

@kn100 any updates?
I've noticed that recent PR added support for neststandard1.6, why can't You add both?
netstandard2.0 has a smaller dependency tree, so it is preferred by many developers.
Take a look at how RabbitMQ did it:rabbitmq/rabbitmq-dotnet-client#428 (comment)

[Misiu]

@damdo any updates?

[damdo]

Hey all! So currently the library supports .NET standard 1.6, but yes .NET standard 2.0 (and thus .NET Core 2.0) is on our radar. We are currently focused on improving certain behaviours of the library / fixing some issues, but extending the compatibility is next 👍

[elverkilde]

This issue was fixed in #104 which was released as version 2.0.0. Please be aware that this is a major release, with several breaking changes. We have written a migration guide here:

https://github.com/pusher/pusher-websocket-dotnet#migrating-from-version-1-to-version-2