Change message protocol with Azure Management SDK

Hi,

I have a question regarding Microsoft.Azure.SignalR.Management package.

Is there a way to change the protocol (MessagePack, NewtonSoftJson, Protobuf, …) ? (like with a ‘classic’ SignalR client)

After reading the code, it seems that, when we create a HubContext with CreateHubContextAsync there is a hardcoded AddSignalRCore() so we cannot add protocol options.

https://github.com/Azure/azure-signalr/blob/6faf565144c0bacc31d001cda3c2ca3dbc78602b/src/Microsoft.Azure.SignalR.Management/ServiceManager.cs#L55

Is there a way change the default serialisation protocol when using SignalR Management SDK ? If no, do you plan to add it as a new feature ? Do you want a PR to be able to add options to SignalR Management ?

Thanks !

[arek-avanade]

@dmitrykarnitski As a workaround you could set a global default serializer settings for Newtonsoft.JSON in your startup file:

            JsonConvert.DefaultSettings = () => new JsonSerializerSettings
            {
                ContractResolver = new CamelCasePropertyNamesContractResolver()
            };

[wanlwanl]

The management sdk always use MessagePack to send messages, the signalr service will convert to the correct protocal (only support json/messagepack) to the signalr client. So the only thing you need to care about is the signalr client’s protocol. For example, you can try to use MessagePack in signlar client

// message pack
var connection = new HubConnectionBuilder().WithUrl(url).AddMessagePackProtocol().Build();

// json
var connection = new HubConnectionBuilder().WithUrl(url).Build();

and use a management sdk to send message, you will see both can receive messages.

For other protocols, I think add a ProtocolProvider to management sdk is fine. When use protocols other than json/messagepack, the sianglr service will not recoginize special messages like close messages. But management sdk doesn’t design to support it, so its ok to simply add a ProtocolProvider in management sdk.