You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Azure Functions packages use the NServiceBus.Newtonsoft.Json package as a dependency and configure the Newtonsoft.Json serializer as the default serializer for function endpoints. This introduces an additional dependency on those JSON related packages which technically we might not need given that the Azure Functions packages target .NET Core 3.1 which has has a built-in JSON support (System.Text.Json).
Community projects like https://github.com/NServiceBusExtensions/NServiceBus.Json have already shown that NServiceBus can work with the built-in Json serializer instead of the Newtonsoft serializer.
It might be necessary to investigate potential compatibility issues given that existing NServiceBus endpoints might still use the Newtonsoft.Json packages instead.
The text was updated successfully, but these errors were encountered:
Currently, the Azure Functions packages use the
NServiceBus.Newtonsoft.Json
package as a dependency and configure the Newtonsoft.Json serializer as the default serializer for function endpoints. This introduces an additional dependency on those JSON related packages which technically we might not need given that the Azure Functions packages target .NET Core 3.1 which has has a built-in JSON support (System.Text.Json).Community projects like https://github.com/NServiceBusExtensions/NServiceBus.Json have already shown that NServiceBus can work with the built-in Json serializer instead of the Newtonsoft serializer.
It might be necessary to investigate potential compatibility issues given that existing NServiceBus endpoints might still use the Newtonsoft.Json packages instead.
The text was updated successfully, but these errors were encountered: