debugging Json.Deserialize error

[germgerm]

i have some code that serializes some data to file that errors when attempting to deserialize
i created a small test app that had no issues doing the same thing
until i use the JsonSerializerOptions from the original code
I copied the working options to the erroring code - it still errored
i serialized the 2 options objects and diff'd them - identical
why would the options object make any difference when they are exactly the same ?

    public static readonly JsonSerializerOptions Jo =  new JsonSerializerOptions
        {
            DefaultIgnoreCondition = JsonIgnoreCondition.WhenWritingNull,
//            WriteIndented = true,
            ReferenceHandler = ReferenceHandler.Preserve,
            Encoder = JavaScriptEncoder.UnsafeRelaxedJsonEscaping,
        };

             dump("Jo",Jo);
             dump("FMdb.Jo",Jo);

             s1 = File.ReadAllText(path);

             Console.WriteLine("Deserialize fmdb File local Jo");
             j3 = JsonSerializer.Deserialize<DbJson>(s1, Jo);
             
             Console.WriteLine("Deserialize fmdb File Fmdb.Jo");
             j3 = JsonSerializer.Deserialize<DbJson>(s1, FMdb.Jo);
             dump("Deserialized", j3);

   ---> System.Text.Json.JsonException: The JSON value could not be converted to System.Collections.Generic.List`1[FretboardMaster.Models.A]. Path: $.As | LineNumber: 0 | BytePositionInLine: 17.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-text-json, @gregsdennis
See info in area-owners.md if you want to be subscribed.

[germgerm]

combing through the 2 projects, the only significant difference i can see is that the one that works is a console app, the other a classlib, changing both to exe makes no difference
same installed and implicitely installed nuget packages all at the same versions
project files are identical excpt for <OutputType>Exe</OutputType>

[germgerm]

i tracked this down to the FMdb.Jo being null at the time of deserialization - my bad for dumping the same local version Jo twice doh! - the problem is somewhere in the static inititialization of FMdb

[germgerm]

solved - moved static members to top of class above static methods

[eiriktsarpalis]

I guess we can close this then?

[germgerm]

all good

…

---- On Wed, 23 Apr 2025 07:52:27 -0400 Eirik Tsarpalis ***@***.***> wrote --- I guess we can close this then? — Reply to this email directly, #114655 (comment), or https://github.com/notifications/unsubscribe-auth/AAOHCNZIOALYMLP6BQC5IOT2255HXAVCNFSM6AAAAAB3D4HKYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRUGAZTAMBQHA. You are receiving this because you authored the thread. eiriktsarpalis left a comment #114655 (comment) I guess we can close this then? — Reply to this email directly, #114655 (comment), or https://github.com/notifications/unsubscribe-auth/AAOHCNZIOALYMLP6BQC5IOT2255HXAVCNFSM6AAAAAB3D4HKYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRUGAZTAMBQHA. You are receiving this because you authored the thread.