Add efmig to Tools section #4592
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My proposal is to add efmig to Tools section.
I've been using it for my daily professional and personal work for more than 2 years now.
I've covered the most popular use cases such as creation of migrations code or generation of scripts as well as support for rollbacking.
It also plays well when working with different dotnet-ef/.NET Runtime/EF Core versions as it uses local versions for everything.
The additional advantage is that it allows to drop dependency on
Microsoft.EntityFrameworkCore.Designin the project itself, it also works well with multiple DbContexts in the single .csprojI believe the community would like to try out alternatives to the dotnet-ef CLI interface.