Provide a way to pin certain packages to a specific repository (source pinning)

[ghost]

I want to be able to say to only use a particular repository for one package, and stick to nuget.org for the others.

Example:

I've got https://dotnet.myget.org/F/dotnet-core/api/v3/index.json enabled so I can use Microsoft.Packaging.Tools.Trimming.

Unfortunately this means a whole lot of other pre-alpha packages show up as the "latest" versions available because there's no way to set priorities or preferences for package sources

maintainer edit

Design available at #10660

[jainaashish]

Can you explain your scenario and requirement in more details? And tell us what mode NuGet UI or PMC, you used more often for such operations?

We know there is no explicit gesture to lock down a certain package from a specific repository but there are still varies ways to achieve it like you can always select a specific source to get the updates or enable/disable specific sources to do the same. And we're also working on some new features like repeatable build with package verification which cover scenarios to make sure that customer always get the same package irrespective of repository (by relying on the hash of the package).

[mwwhited]

How about when your contract library is served from a Nuget repository and you need a way to have a development local version. The hoops that must be jumped though are insane when all that would be needed is for the order of the repositories listed to be honored.

[JonDouglas]

Hi everyone,

In an effort to start gathering more input about this issue, we'd like to invite you to schedule 30 minutes with the NuGet team to talk about potential solutions to this problem so we can shape the future of this feature.

Feel free to reserve 30 minutes in the next couple weeks here with the "Source Pinning" service:

https://aka.ms/talktonuget

Thanks!

[devbeard]

Found this issue when investigating if nuget had the same namespace pinning capabilities like npm. Would love to talk to the team, thanks for the opportunity @JonDouglas.

[JonDouglas]

@devbeard Hey Henrik! We actually closed our calls for this about a week ago & are entering the design stage of a proposal. We'd still love any of your feedback on this thread or provided to our other team members through the call you did sign up for! We'll publish a public proposal shortly in a PR & ask those on this thread to help review.

[JonDouglas]

For those on this thread, we've published a proposal to allow you to pin a package namespace to a source. Feel free to provide your feedback directly on the PR.

#10660

[dominoFire]

Mention from https://developercommunity.visualstudio.com/t/NuGet-should-keep-a-reference-to-package/1387876

[nkolev92]

Hey all,

We will be using this issue to track the complete effort mentioned in the package namespaces proposal at #10660.

Note that this is a large feature and some parts may ship partially/experimentally earlier.

[ey250015]

We did a workaround -

1. restore the project/solution using all sources.
2. remove the packages that needed to be from the specific repository.
3. remove other repositories.
4. restore again the project/solution.

our code on docker file:
&& dotnet restore /src/MyProject/MyProject.csproj
&& rm -rf ~/.nuget/packages/certianPackege
&& dotnet nuget remove source nuget.org
&& dotnet restore /src/MyProject/MyProject.csproj
&& dotnet nuget add source https://api.nuget.org/v3/index.json -n nuget.org
&& dotnet restore /src/AllMySolution.sln \

[nkolev92]

@ey250015

Package namespaces functionality will very soon be in early preview.

We'll update this thread when it's available to try out. We'd love to get your feedback.

[chrisraygill]

Hi y'all! Package Source Mapping (previously Package Namespaces) is available to try out in preview! Check out the blog to learn more: https://devblogs.microsoft.com/nuget/introducing-package-source-mapping/

[JonDouglas]

NuGet has released support for this via a new feature called Package Source Mapping. It is included in .NET 6 & NuGet 6.0.

https://docs.microsoft.com/nuget/release-notes/nuget-6.0#source-mapping

Thus we are closing this issue with a 🎉!