-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modernize EF Core tooling #26798
Comments
I've been trying to work with ef core 7 pre release on MAUI and i could notice that iOS is not working. But Android and Windows work. |
Hey @bricelam @ajcvickers, do you folks have some details about what particular will be updated in EF Core 7 CLI tooling? I'm working on the EF Core plugin for Rider and want to introduce some tracked items to include in the new plugin milestone attached to the EF Core 7 release. |
@seclerp This specific issue had to be cut from the 7.0.0 milestone. It's mostly a duplicate of #18840. The big tooling change in EF7 was support for T4 templates. See the docs for details. You could add a UI gesture for |
Thanks! Can't find |
https://github.com/dotnet/efcore/tree/release/7.0/src/EFCore.Templates The source for the package. It is in daily builds not yet released to nuget. |
Does T4 supports NuGet references via "assembly" directive in general? It will be cool if T4 spec exists somewhere. |
Not exactly a spec, but there's a good description of T4 here: https://docs.microsoft.com/visualstudio/modeling/writing-a-t4-text-template |
But no, NuGet wasn't a thing when T4 was designed. Regardless, the TeaFour plugin should still be able to look for matching assemblies inside installed NuGet packages. |
.NET platforms have evolved since we first introduced tooling for migrations, database scaffolding, etc. in EF Core 1.0. We plan to update the tooling architecture to better support new platforms, like .NET MAUI, and to streamline the process in areas such as the use of multiple projects. This includes providing better feedback when things go wrong, better integration with logging, performance, and new sugar.
The text was updated successfully, but these errors were encountered: