Skip to content
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

MSBuild VSIX should depend on NuGet VSIX that delivers core logic #3852

Closed
rainersigwald opened this issue Oct 11, 2018 · 1 comment
Closed
Assignees
Labels
Milestone

Comments

@rainersigwald
Copy link
Member

See details in NuGet/Home#7390. Moving the manifest would need a coordinated change here and in NuGet.Client.

@rainersigwald
Copy link
Member Author

IIRC offline we decided that this was sufficiently core functionality that instead of moving the manifest we should make the MSBuild vsix depend on the NuGet VSIX that delivers the resolver.

@rainersigwald rainersigwald changed the title NuGet VSIX should ship Microsoft.Build.NuGetSdkResolver manifest MSBuild VSIX should depend on NuGet VSIX that delivers core logic Dec 13, 2018
@rainersigwald rainersigwald added this to the MSBuild 16.0 milestone Dec 13, 2018
rainersigwald added a commit to rainersigwald/msbuild that referenced this issue Jan 31, 2019
Fixes dotnet#3852 by ensuring that NuGet's tasks and targets are present
wherever MSBuild itself is, since common.targets now depends on NuGet.

Closes NuGet/Home#7390.
@rainersigwald rainersigwald self-assigned this Feb 6, 2019
rainersigwald added a commit that referenced this issue Feb 8, 2019
Fixes #3852 by ensuring that NuGet's tasks and targets are present
wherever MSBuild itself is, since common.targets now depends on NuGet.

Closes NuGet/Home#7390.
rainersigwald added a commit that referenced this issue Feb 8, 2019
Fixes #3852 by ensuring that NuGet's tasks and targets are present
wherever MSBuild itself is, since common.targets now depends on NuGet.

Closes NuGet/Home#7390.
@AR-May AR-May added the triaged label Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants