Hey @kirk-marple - thanks for raising the issue. Strange that you can't upgrade as System.Text.Json v7.0.0 targets .NET 6 so I don't know why it wouldn't be working for you.

Are you hitting a specific error when upgrading to Schema.NET v12 due to this?

Hi @Turnerj, downstream from this I'm using Azure Durable Entities, which isn't supported in .NET 7. I've run into dependency issues where if any 7.x.x .NET assemblies get pulled in, it causes problems finding other assemblies or has missing method exceptions. (Has happened with other packages than Schema.NET.)

So for now I've been keeping all my dependencies clear of anything 7.x.x, and avoiding any problems, until they release the next major version of Durable Entities (hopefully with .NET 8).

After talking with some other .NET developers, I think I understand what is going on. Basically Azure Durable Entities is (kinda) replacing our v7 libraries with v6 ones which, through binary breaking changes, causes a whole bunch of problems.

So its less the libraries causing the problem but rather the dumb setup with Azure Durable Entities (and certain other Azure products - I think I remember Azure Functions previously having the same problem come to think of it).

Anyway, I'll get a PR up shortly for optionally having the .NET 6 references for .NET 6 and the .NET 7 references for .NET 7.

I just got bitten by this on another library. I have to check every package update now to see if it's bringing in System.Text.Json 7.0.x. If it happens, my Azure Functions won't load. Thankfully I learned how to use obj/project.assets.json to see where the references come from.

Appreciate you getting this resolved, and look forward to incorporating the new library.

I didn't know that the .NET libraries are tied to the .NET version. @Turnerj Can you share the resource you mention to learn about this?