Allow default serializer to be changed

[andreasohlund]

Technically I think you could hack it today by changing it in a feature that has DependsOn("SerializationFeature") but with this change ASB/ASQ can change it in TransportDefinition.Initialize using settings.SetDefault<SerializerDefinition>(new JsonSerializer()) which seems more resonable.

[danielmarbach]

Still [WIP]? looks like done.

[andreasohlund]

WIP removed @Particular/nservicebus-maintainers please review

[bording]

👍 Looks good to me. Should be a useful change for ASB/ASQ.

[SimonCropp]

So i change transports and my serialization changes? If so you are crossing the streams.

[danielmarbach]

Maybe we need to bite the bullet and make the serializer mandatory

[bording]

I'm all for making it mandatory if we'd rather not let transports choose their own default serializer.

[bording]

Seems like there are some valid reasons for not making it mandatory here though.

[andreasohlund]

So i change transports and my serialization changes? If so you are crossing the streams.

Not saying that's good this but that's how it works today.

Note that we're just saying to hold of with this for v6, the plan is to do it in v7

[Scooletz]

After skimming through the code of PR, it looks that ASQ code handling serialization could be simplified now to the previous shape. I'll create a separate issue for that (it doesn't have to be in the v6 scope though).