-
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
Consider using NuGet's buildTransitive folder #14531
Labels
area-tools
closed-no-further-action
The issue is closed and no further action is planned.
punted-for-3.0
punted-for-6.0
punted-for-7.0
Originally planned for the EF Core 7.0 (EF7) release, but moved out due to resource constraints.
type-enhancement
Comments
25 tasks
I don't think this is relevant after PR #34574. AFAIK, there are no MSBuild props/targets files anymore. Feel free to close if you can't think of any either. (Some may have been added for AoT) |
Closing this for now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-tools
closed-no-further-action
The issue is closed and no further action is planned.
punted-for-3.0
punted-for-6.0
punted-for-7.0
Originally planned for the EF Core 7.0 (EF7) release, but moved out due to resource constraints.
type-enhancement
See Allow package authors to define build assets transitive behavior.
We have some MSBuild assets in EFCore.Design. We should weigh the advantages and disadvantages of making them transitive.
We should also take another look at the way dotnet-ef reads project metadata to see if we can improve it using this feature.
The text was updated successfully, but these errors were encountered: