It might be handy to find out whether newer versions of the .NET global tools currently installed on your machine is available. However, the .NET command-line tools do not provide a built-in way for you to report on outdated NuGet packages of the global tools.
dotnet-tools-outdated is a global tool, that allows you to quickly report on any outdated global tools currently installed on your machine.
The out-of-box command for listing all the global tools is typed as follows:
dotnet tool list -gPackage Id Version Commands
------------------------------------------------------------------------------
apiport 2.8.14 ApiPort
dotnet-tools-outdated 0.5.2 dotnet-tools-outdated
dotnet-try 1.0.19553.4 dotnet-try
project2015to2017.migrate2019.tool 4.1.3 dotnet-migrate-2019
try-convert 0.7.210903 try-convert
upgrade-assistant 0.2.212405 upgrade-assistant
It greatly tells about the installed version. Hovewer, it does not inform if a package is outdated.
The dotnet-tools-outdated provides such info just by typing:
dotnet-tools-outdatedPackage Id Current Available
---------------------------------------------------------
dotnet-tools-outdated 0.5.2 0.6.0
dotnet-try 1.0.19553.4
try-convert 0.7.210903 0.9.232202
upgrade-assistant 0.2.212405 0.3.255803
It lists just the packages which are outdated in a meaning, that it can be updated to a higher version or are obsolete (marked as unlisted - e.g. dotnet-try above). Or the output is just empty, if there is no outdated global tool.
Download and install the .NET 6 SDK or .NET 8 SDK currently in LTS (Long Term Support) or newer (or between). Once installed, run the following command:
dotnet tool install -g dotnet-tools-outdatedIf you already have a previous version of dotnet-tools-outdated installed, you can uptdate to the latest version using the following command:
dotnet tool update -g dotnet-tools-outdatedSupposing rarelly, but in case of the older .NET Core SDK (up to .NET Core 2.1), please install/update to the version lesser than 0.6.2. e.g:
dotnet tool install -g --version 0.5.2 dotnet-tools-outdateddotnet-tools-outdated -hdotnet-tools-outdated
Usage: dotnet-tools-outdated [options]
Options:
--version Show version information
-?|-h|--help Show help information
-t|--toolPath Custom location of the (globally) installed .NET Core tools
-n|--name Check just one package with the given name
-f|--format Output format. xml, json, or table are the valid values. (Default: table)
-ni|--noIndent No indent (For the json format so far)
-o|--output Output file path. (Default: stdout)
-pre|--prerelease Check also pre-released versions
--utf8 Output UTF-8 instead of system default encoding. (no bom)
Notes:
- the output is empty in case of all the installed packages up-to date
- in case of unlisted (deprecated) NuGet package, it does not have the "Available" version column value (e.g. dotnet-try below)
dotnet-tools-outdatedPackage Id Current Available
---------------------------------------------------------
dotnet-tools-outdated 0.5.2 0.6.2
dotnet-try 1.0.19553.4
try-convert 0.7.210903 0.9.232202
upgrade-assistant 0.2.212405 0.3.255803
Notes:
- as seen bellow it shows much more info about installed global tools including these which aren't updated.
- IsOutdated informs whether the installed golbal tool is/is not outdated
- BecomeUnisted informs the installed golbal tool is/is not set as deprecated, alias unlisted at the NuGet repo)
- in case of unlisted (deprecated) NuGet package, it does not have the "Available" version column value (e.g. dotnet-try below)
dotnet-tools-outdated -f json{
"outdatedPackages": [
{
"IsOutdated": false,
"BecomeUnlisted": false,
"Directory": "C:\\Users\\user\\.dotnet\\tools\\.store\\apiport",
"PackageName": "apiport",
"CurrentVer": "2.8.14",
"AvailableVer": "2.8.14"
},
{
"IsOutdated": true,
"BecomeUnlisted": false,
"Directory": "C:\\Users\\user\\.dotnet\\tools\\.store\\dotnet-tools-outdated",
"PackageName": "dotnet-tools-outdated",
"CurrentVer": "0.5.2",
"AvailableVer": "0.6.2"
},
{
"IsOutdated": true,
"BecomeUnlisted": true,
"Directory": "C:\\Users\\user\\.dotnet\\tools\\.store\\dotnet-try",
"PackageName": "dotnet-try",
"CurrentVer": "1.0.19553.4",
"AvailableVer": ""
},
{
"IsOutdated": false,
"BecomeUnlisted": false,
"Directory": "C:\\Users\\user\\.dotnet\\tools\\.store\\project2015to2017.migrate2019.tool",
"PackageName": "project2015to2017.migrate2019.tool",
"CurrentVer": "4.1.3",
"AvailableVer": "4.1.3"
},
{
"IsOutdated": true,
"BecomeUnlisted": false,
"Directory": "C:\\Users\\user\\.dotnet\\tools\\.store\\try-convert",
"PackageName": "try-convert",
"CurrentVer": "0.7.210903",
"AvailableVer": "0.9.232202"
},
{
"IsOutdated": true,
"BecomeUnlisted": false,
"Directory": "C:\\Users\\user\\.dotnet\\tools\\.store\\upgrade-assistant",
"PackageName": "upgrade-assistant",
"CurrentVer": "0.2.212405",
"AvailableVer": "0.3.255803"
}
]
}
git clone https://github.com/rychlmoj/dotnet-tools-outdatedcd dotnet-tools-outdated/src/DotNetToolsOutdateddotnet pack -c release -o nupkgOutput is located in src/DotNetToolsOutdated/nupkg
dotnet tool uninstall -g dotnet-tools-outdatedSince the versions 0.6.0> the dotnet-tools-outdated are going to be ported for the available .NET LTS scheme . (Currently the .NET 6 and .NET 8) This is on behalf of minimizing the size of the package. It is also supposed, folks who using this usually care about the updated versions of the global tools, and don't' need the older version of the .NET SDK.
However if a relly a neeed of environment with an older .NET SDK, then please install the following lower version (There is no functionality change/bug fixings in the current version comparing up to the 0.5.2 version)
- 0.6.0 - if a need to run under the .NET 3.1 (and no .NET 6> SDK is present.)
- 0.5.x - if a need to run under the .NET Core 2.1