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

nuget restore warnings can't be suppressed with NoWarn in Visual Studio #13571

Closed
FixBo opened this issue Jun 24, 2024 · 1 comment · Fixed by NuGet/NuGet.Client#5869
Closed
Labels
Priority:1 High priority issues that must be resolved in the current sprint. Product:VS.Client RegressionFromPreviousRTM A regression from the last RTM. Example: worked in 6.2, doesn't work in 6.3 Style:PackageReference Type:Bug
Milestone

Comments

@FixBo
Copy link

FixBo commented Jun 24, 2024

NuGet Product Used

Visual Studio Package Management UI, Visual Studio Package Manager Console

Product Version

17.10

Worked before?

17.9

Impact

It's more difficult to complete my work

Repro Steps & Context

Add multiple nuget sources and set ManagePackageVersionsCentrally to true.

Visual Studio show restore error even if <NoWarn>NU1507</NoWarn> specified for project.

There is no issues when using dotnet restore or msbuild.

Only legacy projects type affected.

Verbose Logs

NU1507: Warning As Error: There are 2 package sources defined in your configuration. When using central package management, please map your package sources with package source mapping (https://aka.ms/nuget-package-source-mapping) or specify a single package source. The following sources are defined: nuget.org, dotnet-tools
Failed to restore ****** (in 1,08 sec).
NuGet package restore failed. Please see Error List window for detailed warnings and errors.
@FixBo
Copy link
Author

FixBo commented Jun 24, 2024

NuGet/NuGet.Client#5869

@zivkan zivkan added Priority:1 High priority issues that must be resolved in the current sprint. Product:VS.Client Style:PackageReference RegressionFromPreviousRTM A regression from the last RTM. Example: worked in 6.2, doesn't work in 6.3 and removed Triage:Untriaged labels Jun 25, 2024
@zivkan zivkan added this to the 6.12 milestone Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:1 High priority issues that must be resolved in the current sprint. Product:VS.Client RegressionFromPreviousRTM A regression from the last RTM. Example: worked in 6.2, doesn't work in 6.3 Style:PackageReference Type:Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants