Question 1

How do I automatically update all outdated NuGet packages with dotnet-outdated?

Accepted Answer

Run `dotnet outdated -u auto` on your project path; it will upgrade packages to the latest versions based on your version lock settings. You can also use `-u prompt` for interactive upgrades.

Question 2

What's the difference between dotnet-outdated and Visual Studio's NuGet Package Manager?

Accepted Answer

dotnet-outdated is a CLI tool focused on automation and CI/CD integration, offering scriptable updates and reports. Visual Studio provides a GUI for manual, interactive management within the IDE.

Question 3

Why does dotnet-outdated modify unrelated parts of my .csproj file during upgrades?

Accepted Answer

This occurs because dotnet-outdated uses the `dotnet add package` command for updates, which can reformat project files. The tool itself doesn't directly edit files, as explained in the FAQ.

Question 4

How to configure dotnet-outdated for a private Azure DevOps feed?

Accepted Answer

Use a credential provider like the Azure Artifacts provider and set the DOTNET_HOST_PATH environment variable. Add the feed via NuGet CLI with authentication, as detailed in the secure feeds section.

Question 5

Can I use dotnet-outdated in a Docker container for CI/CD?

Accepted Answer

Yes, install it as a global tool in your Docker image with `dotnet tool install`, and run it with options like -f to fail builds on updates. Ensure the .NET SDK and any required environment variables are configured.

Question 6

How to exclude test packages from dotnet-outdated analysis?

Accepted Answer

Use the `--exclude` option with filter strings, e.g., `dotnet outdated --exclude test` to skip packages containing 'test' in their names. This is case-insensitive and can be applied multiple times.

Dotnet outdated

What is Dotnet outdated?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions