PackageSourceMapping config/source command additions

[nkolev92]

Child of #6867.

This covers adding the respective dotnet.exe and nuget.exe commands to edit the config namespaces.

[nkolev92]

cc @JonDouglas

[Zastai]

With a Visual Studio now released that actively requires source mapping when using central version management with more than one source, it'll be more important to be able to do this.

[ransagy]

Is there documentation for this change of it being required? So far I've noticed it as a warning only. Seeing as how there are still some open issues on using source mapping (like the very basic restore tasks in Azure Pipelines not supporting it) I'd be surprised if this became a breaking change.

[nkolev92]

The CPM requirement is documented in https://docs.microsoft.com/en-us/nuget/consume-packages/central-package-management#warning-when-using-multiple-package-sources.

like the very basic restore tasks in Azure Pipelines not supporting it

Please note that those tasks are not what the azure devops team recommends anymore.
They want to deprecate that and have people use NuGetAuthenticate and issue direct commands to dotnet.exe the same way you would locally.

[Zastai]

Well, the warning is now documented, yes. What is not documented is why the warning is issued. Is it just a strong recommendation? Or will there be actual breakages if I add NU1507 to NoWarn? If so, what kind of breakages?

Note that given warnings-as-errors is a common thing in release builds, the introduction of the warning is a potentially breaking change, and should probably have been given more visibility in release notes.

[ransagy]

The CPM requirement is documented in https://docs.microsoft.com/en-us/nuget/consume-packages/central-package-management#warning-when-using-multiple-package-sources.

like the very basic restore tasks in Azure Pipelines not supporting it

Please note that those tasks are not what the azure devops team recommends anymore. They want to deprecate that and have people use NuGetAuthenticate and issue direct commands to dotnet.exe the same way you would locally.

Warning and Required are two different things. Will a restore/build break or stop if no source mapping is enabled in any current released VS/NuGet/dotnet CLI?

Also; key word, want to. Which is another new, relatively jarring change esp. if the above is true.

[nkolev92]

I'd appreciate if you folks could file an issue at NuGet/Home with these questions, that way others can discover this discussion.

I'll loop in right people to help answer your questions and concerns.