-
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
Revisit tools architecture #18840
Comments
@ajcvickers System.Commandline has never been released though |
It would only be a private dependency that ships as part of our tool. We wouldn't be the first to do this. 🙂 |
Related to #14531 |
@AndriySvyryd any status update\is getting actively worked on? getting tracked internally? ran into this wonderful bug today, luckily our EF projects are setup weird enough for |
@KLuuKer This issue is in the Backlog milestone. This means that it is not planned for the next release. We will re-assess the backlog following this release and consider this item at that time. However, keep in mind that there are many other high priority features with which it will be competing for resources, see Release planning process. Make sure to vote (👍) for this issue if it is important to you. |
#34574 should fix some of the above issues |
Some ideas:
Can dotnet-ef use the MSBuild object model?See https://github.com/NuGet/NuGet.Client/blob/fe240c4f457b30050e963dc19f916773ddf21d38/src/NuGet.Clients/NuGet.CommandLine/MsBuildUtility.csMakes Tools ignore $(BaseIntermediateOutputPath) #18060 and dotnet ef migrations fail when using custom output paths and separate project/startup-projects #23853 easierConsider shippingEntityFrameworkCore.targets
inbuildTransitive
instead of creating dynamically.The text was updated successfully, but these errors were encountered: