NativeAOT work for 9.0

[roji]

This is a grouping of related issues. Feel free to vote (👍) for this issue to indicate that this is an area that you think we should spend time on, but consider also voting for individual issues for things you consider especially important.

---

Critical

Query

• Precompiled queries #25009 (@roji)
  • Make ParameterExtractingExpressionVisitor capable of extracting paths to evaluatable fragments in the tree #32999 (@roji)
  • Use interceptors to redirect the query to precompiled code #31331 (@roji)
    • Precompiled queries: support value converters #33541 (@roji)
  • Make all SQL expression nodes quotable #33008 (@roji)
  • Stop using materializer expression in query #32923 (@maumar/@roji)
    • Query/AOT: fix remaining AOT materializer exceptions #33383
  • Integrate precompiled query generation into the build process #33103 (@AndriySvyryd)
• Precompiled query inner loop: source generator to warn and fail dynamic queries #32727 (@roji)
• Precompiled queries: pre-generate SQL (2nd part of the query pipeline) #29753 (@roji)
• Annotate the 2nd part of the query pipeline for AOT/trimming #29759 (@roji)
• Make LINQ providers (Queryable) compatible with NativeAOT runtime#79199 (@roji, done in 8.0)
• NativeAOT/trimming compatibility for Microsoft.Data.Sqlite #29725 (done in 8.0)
• [CoreCLR] Implement support for UnsafeAccessorAttribute runtime#86161 (runtime API to access private fields efficiently, done in 8.0)
• NativeAOT work npgsql/npgsql#4764 (done in 8.0)

Other

• NativeAOT: get to zero warnings #33478 (@AndriySvyryd)
• Allow stripping away all model building code to reduce application size #29755 (@AndriySvyryd)
• Generate compiled relational model #24896 (@AndriySvyryd)
• Make change tracking and the update pipeline compatible with AOT/trimming #29761 (@AndriySvyryd)
• Warning/error when not using compiled model with NativeAOT (@AndriySvyryd)
• Allow to execute migration operations at runtime with Improve Migrations Projects #19694
• Add feature switches to reduce app size #24901

Out of scope for EF9

• In precompiled operator interceptors, access closure fields via unsafe accessor when possible #33418
• AOT: support dynamically-generated queries #29760
  • Annotate the 1st part of the query pipeline for trimming #32734
• Add an option to publish the migration bundle for NativeAOT #31332
• Allow stripping away the expression tree interpreter (query pre-processing) #29858
• AOT: Support compiled queries #29764
• Consider removing the partial trimming annotations introduced in EF Core 7.0 #29763
• Improve trimming support for EF Core apps to reduce application size #21894
• Remove LINQ usage to reduce application size #33766
• Improvements to SQL generation (#29753):
  • Precompiled queries: pregenerate relational commands via IRelationalCommandBuilderFactory #33516
  • Precompiled queries: calculate the NRT status of complex expressions in the funcletizer #33508
  • Precompiled queries: take into account the NRT status of parameters introduced in query filters #33509
• Precompiled queries: lift objects to make them common across query interceptors #33515
• Minor work items left for CSharpToLinqTranslator #33639
• Cosmos NativeAOT support #33909

[jeswin]

I know this is tagged 'consider-for-current-release'. But just to confirm, the plan is to ship it with .Net 8 right?

Upvoted. This is the last major piece required to get native code web apps working without losing out on productivity.

[roji]

@jeswin the plan is still to ship experimental support, but it's not yet clear what we'll manage to complete before the work window for 8.0 closes.

[jeswin]

Thanks for the update.

[JOULTICOA]

I opened issue here but maybe that was wrong spot dotnet/core#8704 @roji

I see in issue #29725 some people said it was now working. I can't seem to get the Microsoft.Data.SQLite to work with AOT publish. is there a certain version I should try?

Thank you!

[roji]

@JOULTICOA can you please open a new issue in this repo (not dotnet/core), with the exact versions and full error(s) that you're seeing? Ideally, with a minimal code sample as well.