Steven Bone

Are you sure that the client is attempting to negotiate TLS 1.3? A network trace may help determine this. If a proxy is involved this is known to be problematic....

I think this is a good time to consider this. Microsoft just released their new [Open-source library guidance](https://docs.microsoft.com/en-us/dotnet/standard/library-guidance) and advise strong naming. This is one of a ever-smaller handful of...

Apologies for jumping in here, but I think it is important to understand the design, operation, and limitations of the underlying technology WebSockets are based on. Please pause a moment...

Perhaps CallOptions could be used (the internal property `TimeoutMili`). Then in `ClientInvocationHandler` the `CallOptions` can be provided to `WaitForResult` and `AwaitForResult`, the latter of which could start like so: Task...

Hello @CapAdv! In this case, async/await is your friend, and it must be done on both callee and caller sides. I am oversimplifying this and therefore am less than 100%...

@golukas, I think you need to reevaluate what it is you are trying to do with this and reconcile this with what is happening under the hood. WebSockets in general...

As per [this documentation issue](https://github.com/dotnet/docs/issues/5756) the behavior for UWP is 'correct' and not a bug. Therefore we should fix our defaults as proposed. > The resource manager uses / for...

I'm seeing this as well in both VS2017 and VS2019 with Version 1.0.1. It did work flawlessly on VS2019 the first time after it was installed, subsequent opening of VS2019...

After a bit of accidental messing around, I think I determined a pattern. If you have the Pending Changes window popped-out and visible when you close Visual Studio, it will...

Apologies - I somehow missed this issue. The error code of '-2147024882' is a Win32 error code for ERROR_OUTOFMEMORY 'Not enough storage is available to complete this operation.' A few...