dotnet-nuget-config-get(1)

💖 dotnet-nuget-config-get 💖

okay bestie, welcome to dotnet-nuget-config-get(1) — that's the manual page name, it lives in the .NET Documentation set, and it is genuinely one of the most underrated little commands out here. no cap.

✨ heads up ✨ This article applies to: ✔️ .NET 8.0.2xx SDK and later versions. so if you're on something older, this is not your moment, sorry babe 🫶

---

🌸 NAME 🌸

dotnet-nuget-config-get — Gets the NuGet configuration settings that will be applied.

like... it goes and finds out what config is actually gonna hit you. the effective one. the real one. the main character config. 💅

---

✨ SYNOPSIS ✨

dotnet nuget config get <ALL | CONFIG_KEY> [--show-path] [--working-directory <DIRECTORY>]

dotnet nuget config get -h|--help

two shapes, pick your fighter: either you ask for <ALL | CONFIG_KEY> (with optional --show-path and --working-directory <DIRECTORY>), or you just yell for help with -h / --help. that's it. that's the whole vibe. 🦋

---

💜 DESCRIPTION 💜

The dotnet nuget config get Gets the NuGet configuration settings that will be applied from the config section.

(not me reading that sentence back three times 😭) — the point is: this command tells you which NuGet configuration settings are actually going to apply, pulling them out of the config section. no guessing, no "well maybe it's that file". it just tells you. iconic behaviour fr fr.

---

🎀 ARGUMENTS 🎀

• ALL — Get all merged NuGet configuration settings from multiple NuGet configuration files that will be applied, when invoking NuGet command from the working directory path. yes bestie, merged — every file that matters, blended together into one final answer. it's giving smoothie energy 🍓
• CONFIG_KEY — Get the effective value of the specified configuration settings of the config section. so you name the key, it hands you the value that actually wins. one key, one answer, no drama. ✨

---

👑 OPTIONS 👑

• --show-path — Indicate that the NuGet configuration file path will be shown beside the configuration settings. so instead of just what the setting is, you also get where it came from. receipts!! 🧾💅
• --working-directory <DIRECTORY> — Specifies the directory to start from when listing configuration files. If not specified, the current directory is used. so you can point it somewhere else and it'll start its little journey from there. and if you don't say anything? current directory. default behaviour, no notes. 🫶
• -?|-h|--help — Prints out a description of how to use the command. the classic cry for help, and it always answers. 💖

---

🌈 EXAMPLES 🌈

1. Lists all the Nuget configuration settings being applied to the current directory:

dotnet nuget config get all

like, show me EVERYTHING. the full fit check. 🔥

2. Lists the repositoryPath value from the config section being applied to the specified directory:

dotnet nuget config get repositoryPath --working-directory "C:/working-directory"

see how we're grabbing one specific key and pointing --working-directory at "C:/working-directory"? chef's kiss. one value, one path, zero confusion. 😌

---

🦋 SEE ALSO 🦋

• nuGet.config reference

go read it, iykyk. it's the lore behind all of this. 📚✨

---

💀 lowkey important reminder: when you don't pass --working-directory, the current directory is used. that's it. that's the caveat. carry on bestie.

---

and that's the whole page, no crumbs left behind 🍓 — this was dotnet-nuget-config-get(1) from the .NET Documentation, dated 2025-06-13. mwah, go forth and get your config. 💜✨