You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any plans to support pre-generated binding for entity models (pre-generated at compile time queries, code for populating entity values etc)?
For .NET Native on UWP and especially for local database access on mobile devices in UWP using of pre-generated code would greatly optimize performance.
.NET Native on UWP have issues with reflection speed and don't support IL code generation and JIT at run-time. LINQ Expressions isn't compiled to IL, but interpreted. LINQ Expressions performance on .NET Native isn't good. ARM mobile devices require good optimization as ARM CPU isn't as powerful as desktop x86 CPU.
The text was updated successfully, but these errors were encountered:
Note for triage: There is overlap between this issue and the existing #1906 and #241 (and also between the latter two). But there is good information here about things we have discussed doing but that are not called out in the existing issues.
I think we could probably track compiled models and any code we want to pre-generate (e.g. using Roslyn) in just one issue. We should decide which issue to keep.
Any plans to support pre-generated binding for entity models (pre-generated at compile time queries, code for populating entity values etc)?
For .NET Native on UWP and especially for local database access on mobile devices in UWP using of pre-generated code would greatly optimize performance.
.NET Native on UWP have issues with reflection speed and don't support IL code generation and JIT at run-time. LINQ Expressions isn't compiled to IL, but interpreted. LINQ Expressions performance on .NET Native isn't good. ARM mobile devices require good optimization as ARM CPU isn't as powerful as desktop x86 CPU.
The text was updated successfully, but these errors were encountered: