I’ve been enjoying the addition of dotnet CLI global tools and figured I’d blog the ones I use. I’ll also include a PowerShell script that is used to install them (or, if they’re installed, update them).

The list is current as of this writing, but you can visit the gist (below) to see the set of tools I’m using at any given time.

• dotnet-depends: Shows the dependency tree for a .NET project.
• dotnet-outdated: Shows outdated packages referenced by a .NET project.
• dotnet-format: Formats code based on EditorConfig settings.
• dotnet-script: Run C# script (.csx) files.
• dotnet-symbol: Download symbols from the command prompt. [I’m still trying this one out to see if I use it much or like it.]
• dotnetsdkhelpers: A global tool version of the original SDK installer helpers that addresses the need for external tools and fixes a couple of bugs with the original.
• gti: Install plugins from a .gti file/manifest. [I’m still trying this one out to see if I like it. If it’s good, I can replace my PowerShell script with a manifest.]
• microsoft.web.librarymanager.cli: dotnet CLI access to the libman dependency manager for JS.

Here’s the gist with the PowerShell script that I use to install these: