Install
.NET CLI
dotnet add package Fake.Tools.GitVersion --version 5.6.0
Package Manager Console
Install-Package Fake.Tools.GitVersion -Version 5.6.0
PackageReference
<PackageReference Include="Fake.Tools.GitVersion" Version="5.6.0" />
Frameworks
Dependencies
Fake.Core.Environment
[5.6.0, )
.NETFramework4.6
Fake.Core.Process
[5.6.0, )
.NETFramework4.6
Fake.IO.FileSystem
[5.6.0, )
.NETFramework4.6
Newtonsoft.Json
[11.0.2, )
.NETFramework4.6
Fake.Core.Environment
[5.6.0, )
.NETStandard1.6
Fake.Core.Process
[5.6.0, )
.NETStandard1.6
Fake.IO.FileSystem
[5.6.0, )
.NETStandard1.6
Newtonsoft.Json
[11.0.2, )
.NETStandard1.6
Fake.Core.Environment
[5.6.0, )
.NETStandard2.0
Fake.Core.Process
[5.6.0, )
.NETStandard2.0
Fake.IO.FileSystem
[5.6.0, )
.NETStandard2.0
Newtonsoft.Json
[11.0.2, )
.NETStandard2.0
Adoption guide
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.
Compatibility metadata lists 3 target frameworks; confirm the exact target used by your application.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.