Layomi Akinrinade

@krwq I'll get this fix in & address test feedback in a follow up.

Looks like this issue can be closed following https://github.com/aspnet/Benchmarks/pull/1698.

Yes this is [known](https://github.com/dotnet/runtime/blob/00f37bc13b4edbba1afca9e98d74432a94f5192f/src/libraries/System.Text.Json/tests/System.Text.Json.SourceGeneration.Tests/Serialization/PropertyVisibilityTests.cs#L62-L87), for the reason Eirik mentioned - we cannot reference an init-only setter in generated code outside of object initialization/construction. > do you think it might make...

I agree that the current behavior of failing silently is not good, however the reflection-based approach feels like too much of a hack. For 6.0 I propose we throw `NotSupportedException`...

@SilentCC, yup go for it!

## Configuration binding source generator improvements In [Preview 3](https://devblogs.microsoft.com/dotnet/announcing-dotnet-8-preview-3/#introducing-the-configuration-binding-source-generator), we introduced a new source generator to provide AOT and trim-friendly [configuration in ASP.NET Core](https://learn.microsoft.com/aspnet/core/fundamentals/configuration). The generator is an alternative to...

## Introducing the configuration binding source generator https://github.com/dotnet/runtime/pull/82179 [Application configuration in ASP.NET Core](https://learn.microsoft.com/aspnet/core/fundamentals/configuration/?view=aspnetcore-7.0) is performed using one or more configuration providers. Configuration providers read data (as key-value pairs) from a...

cc @MihaZupan any ideas here?