I was just wondering why the choice of Expressions to implement serialize?

[IOnlyFetchBranches]

It makes it a little hard for me when i'm trying to debug and find the source of a null pointer...
is this faster or provide some benefit i can't figure out? Thanks

Though, to be fair, i think its because im using nullable ints in 48, it seems to die when i step through the debug assembly soon after reading from the int? property ( first item of an array of record types, within my top level contract type) But honestly i have no clue because it's just hopping all over the place.

I am using a debug version that i built, so just figured i'd ask here.

Thanks.

[IOnlyFetchBranches]

Looks like it is registering the schema btw, but having issues when writing bytes for int? field nested within object within an array of objects, within the main object...

[dstelljes]

Expressions are indeed used for performance reasons. Reflection is relatively slow; by building serializers as expression trees, the serializer builder is able to do the expensive reflection work once up front and return a delegate that performs as well as a hand-written serializer.

If you can provide a full stack trace, we may be able to help determine the cause of your issue.

[IOnlyFetchBranches]

Thanks, makes sense. But they are difficult to debug ;(

I figured out what was causing the NPE after stepping through the serialize methods being called by the Expression, rather indirect, but good enough.

Determined it was a buried List that was set to null... Guessing the base 4.8 serializer for chr.avro doesnt like this.

I followed the post to enable nullablereferncetypes all, and i think that fixed it? So far so good.

This is a legacy app, almost as old as i am LOL, so i'm having to validate all of our fields by hand to make sure we dont do that anywhere else.

Thanks for the quick response and love this project. ;)