Command and parameter names may improve or change over time. Please create issues or PRs if you'd like to fix, change or add a command.
Install .NET Core global tool:
dotnet tool install -g dnt
Update the global tool:
dotnet tool update -g dnt
Uninstall the tool:
dotnet tool uninstall -g dnt
Globally install/update via NPM (.NET 4.6.2+ and .NET Core 2.1+):
npm i -g dotnettools
Uninstall global package:
npm uninstall -g dotnettools
By default, all commands search in the current directory for all *.csproj files and apply the command to all of them. The targeted projects or solutions can be changed with the /path:MyProject.csproj parameter.
To list all currently selected projects, call:
dnt list-projects
dnt list-projects /path:MySolution.sln
Available commands:
Possible scenarios to use the tools:
Installs a NuGet package in the selected projects.
Command:
dnt install-packages PackageToInstall [TargetPackageVersion] [/path:ProjectDirectoryPath]
Parameters:
- PackageToInstall
- TargetPackageVersion
- ProjectDirectoryPath
Updates NuGet packages in the selected projects.
Command:
dnt update-packages PackagesToUpdate [TargetPackageVersion] [/path:ProjectDirectoryPath]
Parameters:
- PackagesToUpdate: The package ID to update, also supports * wildcards
- TargetPacketVersion: The targeted package version (default: latest)
- ProjectDirectoryPath
Samples:
Update all packages in the selected projects to the latest version:
dnt update-packages *
Update the Newtonsoft.Json packages in the selected projects to version 10.0.1:
dnt update-packages Newtonsoft.Json 10.0.1
Update all packages which start with MyPackages. to version 2.1.0 in the selected projects:
dnt update-packages MyPackages.* 2.1.0
Increases or changes the package version of the selected projects.
Command:
dnt bump-versions major|minor|patch|revision [number]
Parameters:
- Action: Specifies the version segment to bump (major|minor|patch|revision) by 1 or by the specified number
- Number: The version to bump up to (if not specified: Increase by 1)
Samples:
Bump the minor version of all selected projects by 1:
dnt bump-versions minor
Set the patch version of all selected projects to 18:
dnt bump-versions patch 18
This command switches NuGet assembly references to project references and vice-versa. This is useful when developing applications/libraries which reference own NuGet packages: When developing an application, switch to project references so that all code is editable and debuggable. After finishing the development, create new NuGet package versions, switch back to NuGet references and upgrade to the new NuGet versions.
This command supports .csproj, .vbproj, legacy and SDK-style projects (.NET Core/Standard). Previously it was implemented as a Visual Studio extension: NuGetReferenceSwitcher.
Create a switcher.json file and specify the solution to look for projects, and the NuGet packages to replace with actual projects. The involved projects are only specified by the solution path in the settings file:
Sample: Here we create a switcher file for NSwag which references libraries of NJsonSchema to work on both projects in a single solution:
{
"solution": "NSwag.sln",
"mappings": {
"NJsonSchema": "../../NJsonSchema/src/NJsonSchema/NJsonSchema.csproj",
"NJsonSchema.CodeGeneration": "../../NJsonSchema/src/NJsonSchema.CodeGeneration/NJsonSchema.CodeGeneration.csproj",
"NJsonSchema.CodeGeneration.CSharp": "../../NJsonSchema/src/NJsonSchema.CodeGeneration.CSharp/NJsonSchema.CodeGeneration.CSharp.csproj",
"NJsonSchema.CodeGeneration.TypeScript": "../../NJsonSchema/src/NJsonSchema.CodeGeneration.TypeScript/NJsonSchema.CodeGeneration.TypeScript.csproj"
}
}Then switch to projects in the solution:
dnt switch-to-projects switcher.json
Now all NJsonSchema package references in the NSwag solution are replaced by local project references and the NJsonSchema projects are added to the solution.
After implementing and testing, switch back to NuGet references and update to the latest version:
dnt switch-to-packages switcher.json
dnt update-packages NJsonSchema*
Lists all used packages, transitive packages in the projects and their licenses.
Parameters:
- ExcludeMicrosoft (default: true): Exclude packages which start with Microsoft.*
- ExcludeSystem (default: true): Exclude packages which start with System.*
- IncludeTransitiveDependencies (default: true): Also analyze transitive dependencies (i.e. indirectly referenced packages)
Sample output for NJsonSchema:
Package Version # License License URL
BenchmarkDotNet 0.10.14 1 MIT https://github.com/dotnet/BenchmarkDotNet/blob/master/LICENSE.md
BenchmarkDotNet.Core 0.10.14 4 MIT https://github.com/dotnet/BenchmarkDotNet/blob/master/LICENSE.md
BenchmarkDotNet.Toolchains.Roslyn 0.10.14 1 MIT https://github.com/dotnet/BenchmarkDotNet/blob/master/LICENSE.md
DotLiquid 2.0.254 1 Apache http://www.apache.org/licenses/LICENSE-2.0
NBench 1.0.4 2 Apache https://github.com/petabridge/NBench/blob/master/LICENSE
Newtonsoft.Json 9.0.1 4 MIT https://raw.github.com/JamesNK/Newtonsoft.Json/master/LICENSE.md
NodaTime 2.2.0 2 Apache http://www.apache.org/licenses/LICENSE-2.0
Pro.NBench.xUnit 1.0.4 1 MIT https://raw.githubusercontent.com/Pro-Coded/Pro.NBench.xUnit/master/LICENSE
xunit 2.3.1 7 Apache https://raw.githubusercontent.com/xunit/xunit/master/license.txt
xunit.abstractions 2.0.1 2 Apache https://raw.githubusercontent.com/xunit/xunit/master/license.txt
xunit.analyzers 0.7.0 1 Apache https://raw.githubusercontent.com/xunit/xunit.analyzers/master/LICENSE
xunit.assert 2.3.1 1 Apache https://raw.githubusercontent.com/xunit/xunit/master/license.txt
xunit.core 2.3.1 1 Apache https://raw.githubusercontent.com/xunit/xunit/master/license.txt
xunit.extensibility.core 2.3.1 3 Apache https://raw.githubusercontent.com/xunit/xunit/master/license.txt
xunit.extensibility.execution 2.3.1 1 Apache https://raw.githubusercontent.com/xunit/xunit/master/license.txt
xunit.runner.visualstudio 2.3.1 6 Apache https://raw.githubusercontent.com/xunit/xunit/master/license.txt
YamlDotNet.Signed 5.0.1 1 MIT https://github.com/aaubry/YamlDotNet/blob/master/LICENSE
Looks through all the projects for assembly/DLL references that could instead be project references in the same solution.
The command does make the assumption that the assembly output of a project has the same name as the project.
dnt switch-assemblies-to-projects
Looks for references like
<Reference Include="ProjectA">
<HintPath>..\ProjectA\bin\ProjectA.dll</HintPath>
</Reference>
And replaces with
<ProjectReference Include="..\ProjectA\ProjectA.csproj">
<Project>{B12406B0-0468-4809-91E3-7991800E3ECD}</Project>
<Name>ProjectA</Name>
</ProjectReference>
Enables a project feature in all selected projects.
Command:
dnt enable warnaserror|xmldocs
Parameters:
- Action: Specifies the feature to enable (warnaserror|xmldocs)
Samples:
Handle all warnings as errors in all selected projects:
dnt enable warnaserror
Add another target framework to the selected projects.
Command:
dnt add-target-framework TargetFramework
Parameters:
- TargetFramework: Specifies the target framework to add
Samples:
Add .NET Standard 2.0 target framework to all projects:
dnt add-target-framework netstandard2.0
Deletes all /bin and /obj directories of the selected projects.
It is recommended to add the debug output path "DNT/src/Dnt.NetFx/bin/Debug" to the Path environment variable, or directly start the app with a command.