Skip to main content

Central Package Management - warning NU1507: There are 2 package sources defined in your configuration.

A few weeks ago, I talked about a new NuGet feature, Central Package Management. This allows you to manage your dependencies at the solution level instead of at the project level.

After converting one of my projects to use Central Package Management, I noticed the following warning in Visual Studio:

warning NU1507: 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, company.be.

I get this warning because I have 2 package sources defined, one at the machine level and one at the solution level in my nuget.config.

I could get rid of this warning by using a single package source.Therefore I need to update my nuget.config file to have only 1 package source defined and add a <clear /> statement to not use package sources found at other levels:

Another solution is to use Package Source Mapping as suggested in the warning.

What is Package Source Mapping?

With Package Source Mapping, you can define from which source each package in your solution should be restored. This is important to improve security when you use a mix of public and private package sources and helps you against software supply chain attacks.

To use Package Source Mapping, you need to update your nuget.config file and specify one or more package patterns:

In the example above a packageSourceMapping element was added in which we declared a packageSource element for each source in use. Per source we defined a pattern that(it can be more then one) links the package name to the correct source.

In our example, packages started with company.* will use the private company.be package source. All other packages come from the public nuget.org package source.

If you want to learn more, have a look at the documentation.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more