dotnet
EF Core platforms experience
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.
This an "epic" issue for the theme of improving the EF Core experience in various app models. Specific pieces of work will be tracked by linked issues.
Done in 7.0
- [x] #26799
Backlog
- [ ] #21894
- [ ] #26798
- [ ] #26949
- [ ] #7152
- [ ] #32835
- [ ] #24903
- [ ] #12087
We have good guidance for using EF Core in traditional MVC-like web applications. Guidance for other platforms and application models is either missing or out-of-date. For EF Core 5.0 we plan to investigate, improve, and document the experience of using EF Core with:
- Blazor
- Xamarin, including using the AOT/linker story
- WinForms/WPF/WinUI and possibly other U.I. frameworks
As with is likely to be many small improvements in EF Core, together with guidance and longer-term collaborations with other teams to improve end-to-end experiences that go beyond just EF.
Specific areas we plan to look at are:
- Deployment, including the experience for using EF tooling such as for Migrations
- Application models, including Xamarin and Blazor, and probably others
- SQLite experiences, including the spatial experience and table rebuilds
- AOT and linking experiences
- Diagnostics integration, including perf counters
Some related issues:
https://github.com/dotnet/efcore/issues/329 https://github.com/dotnet/efcore/issues/10963 https://github.com/dotnet/efcore/issues/12087 https://github.com/dotnet/efcore/issues/13099 https://github.com/dotnet/efcore/issues/17223 https://github.com/dotnet/efcore/issues/18908 #19535
WinForms/WPF/WinUI and possibly other U.I. frameworks
Does this include UWP?
@Felix-Dev We're still working out the details here. See https://github.com/dotnet/efcore/issues/19978#issuecomment-589864423 for a longer discussion.