NativeAOT

[murshex]

Can I use RavenDB in a .NET 8 console app compiled with NativeAOT?

[ayende]

I don't believe that we have tested that scenario, but from a client perspective, I think it should work. There is a lot of dynamic stuff inside of RavenDB (from JSON serialization to dynamic code emitting at runtime), but the client code is far simpler.
Would love to hear your report on this.

[SbiCA]

@ayende I gave it a try and realized as an outsider I would say probably not possible without spending at least a few days on it 🥹 to understand the abstractions you put into place for Blittable Reader/Writers.

I really had a tough time to understand how I should write the adapter for
https://github.com/ravendb/ravendb/blob/f9e1a5717e164f37a287107a9ce2831e50575049/src/Raven.Client/Json/Serialization/NewtonsoftJson/NewtonsoftJsonSerializationConventions.cs mainly because it's internal hence can't be use from the outside therefore even if I could re-use things (which I'm not sure if a good idea or practically possible).

In addition I'm also not quite clear if there are implications with using it in a mixed mode e.g. clients using STJ and Newtonsoft at the same time.

I pushed my code here https://github.com/SbiCA/Rebus-NativeAot/pull/1/files (but be aware it doesn't compile).

Happy to help if you guys have further questions but I'd really love to see this (https://blog.martincostello.com/native-aot-make-dotnet-lambda-go-brr/) happening with raven in the mix and generally I think the source generator could be a pref benefit as well

[SbiCA]

@ayende @ppekrol are you guys thinking about making this happen or what's your view points?

[ppekrol]

We would love to take a peek there, but at the moment we are working on wrapping up the 7.0 and 7.1 releases. Using <IsAotCompatible>true</IsAotCompatible> in the csproj yields 200+ warnings. We are very heavily dependent on reflection and dynamics in the Client API, not sure even what would be the scope of work here. Looks a bit like an epic adventure.

[murshex]

It’s probably not that difficult to make the Client API support NativeAOT. System.Text.Json fully supports it.

[ayende]

We are using Newtonsoft by default here.
In general, would love to have Native AOT and System.JSON integrated.

But we are looking at doing that only after the 7.1 time frame (which is probably 4 - 6 months away)

Would be very happy to collaborate / assist if you care to give it a shot