Versioning scheme

Asked

Viewed 476 times

6

In . NET, the assemblies generated have four version numbers. I’ve heard a lot about larger version and smaller version (major version and minor version), and that those would be the first two numbers. I have heard that the third number would be "maintenance" and the fourth would be "revision", but I have also heard (and found on the internet) mentions to the third number as the number of build.

What is the "right" way to interpret numbers? Or is there more than one pattern? And when each number should be incremented?

.net versioning
  • 4

    Have you looked at the http://semver.org/ Given a version number MAJOR.MINOR.PATCH, increment the: 1 MAJOR version when you make incompatible API changes, 2 MINOR version when you add Functionality in a Backwards-compatible Manner, and 3 PATCH version when you make Backwards-compatible bug fixes.

2 answers

4


Form "correct" does not actually exist, but there are some indications from Microsoft.

The MSDN indicates to use the segment form:

<major version>.<minor version>.<build number>.<revision>

Modelled:

  • Major version: Number representing the flow of your application, when your application drastically changes the flow or is redesigned, increments this version.
  • Minor version: Number that represents the increment of improvements and new functionalities, increases when the application is updated with a new functionality.
  • Build version: Build build number, usually incremented automatically by Visual Studio.
  • Revision version: Bugfix number, fixes in general, increments when your application is updated by fix function.

Versões no Padrão Microsoft

Like in Windows itself:

  • Windows XP = 5.1.2600.3
  • Windows Vista = 6.0.6001.1
  • Windows Seven = 6.1.7601.1

1

According to the SEMVER:

(in free translation)

Given a MAJOR.MINOR.PATCH version number, increment:

MAJOR (Main version), when you make changes to the API that break backward compatibility,

MINOR (Secondary version), when you add functionality in a way compatible with previous versions, and finally,

PATCH (Patch version), when you make corrections backward compatible (buggies).

Labels for additional prereleases and metadata of Builds are available as extensions to MAJOR.MINOR.PATCH format.

OBS.:

In the .NET, by default is adopted version with 4 numbers, the third is the Build, and the fourth is Revision Number.

I hope I made myself clear. If you have any questions you can comment at the bottom or take a look at the Semver specification.

  • Could you provide a reference to that information in the box, Alan?

  • 1

    The definitions of . Net or Semver? For Semver : http://semver.org For . NET : http://msdn.microsoft.com/en-us/library/51ket42z(v=vs.110). aspx

  • The "OBS" box, dude! = D

  • 1

    Corrected, chief.

Browser other questions tagged .net versioning

You are not signed in. Login or sign up in order to post.