AOT compatibility, and move to System.Text.Json

[HalvorNygaard]

Is there a plan to move from Newtonsoft.Json to System.Text.Json? Will this make RulesEngine AOT compatible, or is there still other logic relying on reflection? Is there ways to use RulesEngine with AOT today?

[madhon]

any comments @abbasc52 ?

[asulwer]

System.Text.Json is restrictive, has lots of checks in that. lots of work for no real benefit

Migrate from Newtonsoft.Json

[HalvorNygaard]

Well the question was concerning the AOT compatibilty, as Microsoft changed up a lot of internals of ASP.NET to make it AOT compatible, I would guess within a year or two you will have to use aot compilation to get the most out of it. So the benefit would to also be able to use it it projects built for AOT compilation.

Just came across the issue when i tried to compile a .NET app AOT, haven't tested out the proposed fix myself, so I don't know what the implications of swapping the json serializer are.

[asulwer]

swapping would mean reinventing code that Newtonsoft.Json provides and System.Text.Json does not. i am not saying its off the table, maybe a future lite version. regardless this project is dead and my fork is not

[RenanCarlosPereira]

@madhon please check out this PR:
I just migrated it, and everything looks fine 😎

asulwer#32