How to use a different nuget source for debug and release configurations?

Question

How to use a different nuget sources/feeds for Debug configuration and Release configuration?

USE CASE / CONTEXT

A company publishes Debug and Release binaries for the same source code to configuration-specific nuget feeds, and I need to use these internal nugets as dependency for another 2 separate configuration-specific builds. I intend to use this nuget dependency system only with C# projects.

My first idea was to declare configuration-specific nuget sources in the nuget.config file, but I failed doing so.

It is also quite complicated for me to modify every project file on every single branch to accomplish this challenge, since there are thousands of projects organized ('disorganized') into several directories in the company's repository.

Are there also any good suggestions on how to exactly deal with this real-life problem?

You can replace sources in nuget.config in your release build pipeline (assuming you have one, or have a build script that produces "release" build that would do the replacement) and have "debug" sources for consumption by developers by default in your source control. However, having the with the same ids and versions to have different content depending on the source sounds like recipe for trouble. — n0rd
– n0rd, Commented May 16 at 21:29

riQQ · Accepted Answer · 2025-06-23 09:18:57Z

1

Limitation: doesn't work in IDE builds

You can use the property RestoreConfigFile in a Directory.Build.targets file (or in the project files). Directory.Build.props is evaluated before the Configuration property is available.

<PropertyGroup Condition=" '$(Configuration)' == 'Release' ">
  <RestoreConfigFile>$(MSBuildThisFileDirectory)\ReleaseNuGet.config</RestoreConfigFile>
</PropertyGroup>

Alternatively, you can also set the property by passing it as a command line argument to msbuild or dotnet:
/p:RestoreConfigFile=".\ReleaseNuGet.config"

Source: https://github.com/NuGet/Home/issues/5843

edited Jun 23 at 9:18

answered Jun 20 at 8:06

riQQ

13.4k7 gold badges68 silver badges77 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

sɐunıɔןɐqɐp Jun 23 at 8:27

Would that work with Directory.props? I'm not sure if the evaluation of this property happens before or after the Directory.props resolution. The company has thousands of projects in several branches. I'll give this a try and provide feedback later.

riQQ Jun 23 at 9:16

If it doesn't, put it in a Directory.Build.targets file, that should be evaluated late enough.

Collectives™ on Stack Overflow

How to use a different nuget source for debug and release configurations?

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related