Switch JSON serializer usage over to new source generator APIs

[CoffeeFlux]

Until this happens, the default Blazor template will have a size regression: dotnet/runtime#51311

New APIs: dotnet/runtime#45448 (comment)

Initial attempt: https://github.com/eerhardt/aspnetcore/commits/json-tmp

cc: @mkArtakMSFT @eerhardt @layomia

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[mkArtakMSFT]

@MackinnonBuck what is left here to be done?

[MackinnonBuck]

As of #54956, we've started to use the STJ source generator during WebAssembly startup. This was a targeted change whose goal was to improve startup performance. We also scoped the changes to be limited to those that didn't require new public API.

In the future, we could revisit this area by creating new public APIs that enable customers to utilize the STJ source generator for JS interop, persistent component state, etc. We currently have #39839 and #40683 to track specific scenarios that could benefit from supporting the STJ source generator, and we can open new issues in the future for additional scenarios.