CroMagVersion 0.3.5

dotnet add package CroMagVersion --version 0.3.5

NuGet\Install-Package CroMagVersion -Version 0.3.5

This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.

<PackageReference Include="CroMagVersion" Version="0.3.5" />

For projects that support PackageReference, copy this XML node into the project file to reference the package.

paket add CroMagVersion --version 0.3.5

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

#r "nuget: CroMagVersion, 0.3.5"

#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.

// Install CroMagVersion as a Cake Addin
#addin nuget:?package=CroMagVersion&version=0.3.5

// Install CroMagVersion as a Cake Tool
#tool nuget:?package=CroMagVersion&version=0.3.5

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

An MSBuild project integration that makes it easy to keep version numbers synced across all projects in a solution based on a simple date scheme and user provided major / minor version numbers. Provides a single source of truth for versioning, and modifies it at build time as necessary to keep assembly metadata fresh.

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on CroMagVersion:

Package	Downloads
MafHostManager Host Manager for MAF Plugins	54.1K

GitHub repositories

This package is not used by any popular GitHub repositories.

Version	Downloads	Last updated
0.3.5	38,415	2/12/2013
0.3.4	1,466	8/29/2012
0.3.3	1,218	8/29/2012
0.3.2	1,272	7/6/2012

* No more Win32Exception when hg.exe or git.exe not in PATH
       * File generation is now provided through a T4 template instead of via
       an imported MSBuild target. This was necessary to better support
       package restore, and should be a transparent under-the-hood change.
       * Includes MonoDevelops TextTransform.exe to codegen instead of relying
       on anything that ships with Visual Studio
       * Adds a new CROMAG variable that must be defined to generate versioning
       code - by default this is enabled for any non-DEBUG builds
       * Removed the dependency on an msbuild mercurial task
       * Breaking change - no longer emits MSBuild variables $(VersionNumber)
       $(Changeset) $(BuildVersion) or $(RevisionVersion)
       * Minor bugfixes to handle project paths with spaces, and non-standard
       Git and Mercurial locations on disk.
       * Initial DEBUG builds would fail until a RELEASE build generated info