Microsoft.Azure.SignalR.Protocol MessagePack V2 breaking change

[marcodemagalhaes]

Hi

When I upgraded messagepack to v2 the Microsoft.Azure.SignalR.Protocols package started to get error because it implements v1

There are plans to migrate to messagepack v2?

Thanks!

[vicancy]

As dotnet/aspnetcore#18133 (comment), we will follow the same practice to build MessagePack from source to prevent such issues in the future.

[tebeco]

hello @vicancy

Can you enlighten me about the comment you linked.
Are you planning to :

• Use MessagePack as a SubModule + build from source
• Update MessagePack as a Major / Breaking Change version ?

EDIT : see #803

[tebeco]

@marcodemagalhaes
I'm a bit ahead of schedule as it is not "reviewed / merged / released"
But to be clear, once the PR #803 is released
As it look for now, it only "removes" the Transitive dependency from Azure SignalR SDK on MessagePack.
This mean that if you ever use a SignalR Hub + MessagePackHubProtocol, you will be hit by dotnet/aspnetcore#18692
dotnet/aspnetcore#18692 (comment)

So depending on your use of SignalR it self, and the protocol you are using, you might be stuck until AspNetCore 5.x.

If you cannot wait until then, and can add complexity to your project, you might be able to fork the actual implementation of the MessagePackHubProtocol that has been merged in dotnet/aspnetcore on master branch
Please check that this is not in violation of any LICENSE and then update your LICENSE/3rPartNotice... to point to the dotnet/aspnetcore one ... i think ... please ask someone more familiar than me on that

[vicancy]

With generous help offered by @tebeco, v1.4.0 removes the dependency.