-
Notifications
You must be signed in to change notification settings - Fork 255
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
Read PackageReferences from CollectPackageReferences #4967
Comments
As part of this work we will need to ensure that PackageReferences coming from targets/props in packages are ignored. This would cause the first restore to give a different result than the 2nd and 3rd restores. |
emgarten
added a commit
to NuGet/NuGet.Client
that referenced
this issue
Aug 4, 2017
This adds an extension point for MSBuild targets to hook into restore with AfterTargets and BeforeTargets. CollectPackageReferences is called in Visual Studio, NuGet.exe, dotnet restore, and MSBuild restore. Fixes NuGet/Home#4967
This was referenced Aug 4, 2017
Closed
emgarten
added a commit
to NuGet/NuGet.Client
that referenced
this issue
Aug 30, 2017
This adds an extension point for MSBuild targets to hook into restore with AfterTargets and BeforeTargets. CollectPackageReferences is called in Visual Studio, NuGet.exe, dotnet restore, and MSBuild restore. Fixes NuGet/Home#4967
emgarten
added a commit
to NuGet/NuGet.Client
that referenced
this issue
Aug 31, 2017
This adds an extension point for MSBuild targets to hook into restore with AfterTargets and BeforeTargets. CollectPackageReferences is called in Visual Studio, NuGet.exe, dotnet restore, and MSBuild restore. Fixes NuGet/Home#4967
@emgarten What release will this be in - so that we can remove our version? |
@davkean VS 15.4, NuGet 4.4.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Restore should read PackageReferences from
CollectPackageReferences
instead of the items directly.see: dotnet/project-system#653
The text was updated successfully, but these errors were encountered: