NetChris.BuildTools.Versioning 2.0.444415557

NetChris.BuildTools.Versioning

Provides consistent versioning of assemblies and packages

Use

In your project's *.csproj file:

• Set <VersionPrefix /> to the {Major}.{Minor} version of your project
• Add the reference: dotnet add package NetChris.BuildTools.Versioning
• Alternately, directly add the PackageReference in your project, replacing "0.0.*" with the most appropriate package version:

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>netstandard1.1</TargetFramework>

    
    
    <VersionPrefix>0.2</VersionPrefix>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="NetChris.BuildTools.Versioning" Version="0.0.*">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
    </PackageReference>
  </ItemGroup>
</Project>

This relies on this blurb from "Include MSBuild props and targets in a package":

You might want to add custom build targets or properties in projects that consume your package, such as running a custom tool or process during build. You do this by placing files in the form <package_id>.targets or <package_id>.props [...] within the \build folder of the project.

Variables during build

There are a few properties you can set to vary the versioning. These values can also be supplied through environment variables. They are primarily of use in CI/CD scenarios.

References

• SemVer