Tim Bussmann

that behavior mostly seems to rely on the serializer and it's capability to deal with that. Is this the behavior you're seeing on both XML and JSON serializers? How would...

@fjmorel we use SimpleJson internally in NServiceBus and some downstream packages, but for message deserialization, it should use the configured serializer (typically newtonsoft.json or XML). Are you experiencing the same...

> I was just trying to point out that it was a problem with SimpleJson, but that other serializers likely don't have the issue. 👍 we already do have an...

hey @sylvaingirardbe > We're running into more or less the same issue using immutable records in sagadata. What kind of errors do you run into exactly? Does this cause issues...

> If you make the type immutable, or in this case just remove the default ctor, it'll fail with a null reference. Deserializing this type using Newtonsoft or System.Json works...

yeah, the one-line positional record definition doesn't provide an empty ctor (and it seems it can't be configured to get one), so that's a bit unfortunate. This should be enabled...

btw. @sylvaingirardbe what transport and persistence are you using?

it seems those types are excluded by this code: https://github.com/Particular/NServiceBus/blob/6.0.0/src/NServiceBus.Core/Pipeline/Incoming/DeserializeLogicalMessagesConnector.cs#L126 the naming confuses me, since this doesn't seem to be only related to v3? > This seems incorrect. I only...

sending an interface message from v5 yield the following header: ``` NServiceBus.EnclosedMessageTypes HeaderMessage, ConsoleHost4-6, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null ```

(adding this to the v8 milestone for now as KtLO expressed willingness to make this a priority once the v8 window opens up)