System.Text.Json serializer

[DavidBoike]

No description provided.

[andreasohlund]

LGTM apart from some missing API docs.

[SimonCropp]

so will you be writing a upgrade/transition guide for NServiceBus.Json package?

will you submit a PR to NServiceBus.Json with obsolete messages?

[danielmarbach]

Would it make sense to mave the JSon package reference from

  <ItemGroup Condition="'$(TargetFramework)' == 'net472'">
    <PackageReference Include="System.Memory" Version="4.5.5" />
    <PackageReference Include="System.Text.Json" Version="7.0.2" />
  </ItemGroup>

to

  <ItemGroup Label="Public dependencies">
    <PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="7.0.0" />
    <PackageReference Include="System.Diagnostics.DiagnosticSource" Version="7.0.2" />
    <PackageReference Include="System.Security.Cryptography.Xml" Version="7.0.1" />
  </ItemGroup>

? Then we would have the same JSON version in place for all TFMs

[DavidBoike]

@SimonCropp

so will you be writing a upgrade/transition guide for NServiceBus.Json package?

will you submit a PR to NServiceBus.Json with obsolete messages?

Yes to all 😄

[DavidBoike]

FYI @danielmarbach, decided not to apply the V7 package across the board. If we didn't have .NET Framework targets we would probably just not declare the dependency and use the in-box version, at least until we try to do something (like with the source generators) that requires a specific version. So if you close one eye and ignore the net472 stuff now, that's essentially what we have.

[danielmarbach]

Agreed. Currently we also are not using anything of the version specific things so it should be fine