Version Numbers float, decimal or double

I have a document management system where documents can have multiple versions. Each version is saved and users can view version history.

What I would like to know is: What datatype should I use for version numbers? Decimal, Float or Double? I’m using .NET and C#.

  • How should I structure my Git repositories with my .NET Solution?
  • In Git, removing DLL and PDB files that have accidently been committed
  • Securing files in git repository
  • Best practices/guidance for maintaining assembly version numbers
  • How should I use SQL Server Compact Edition in a SharpDevelop project on multiple computers using Git?
  • C# example of downloading GitHub private repo programmatically
  • Version numbers start at 0.1 and each published major version will be rounded to the next whole number. i.e. 0.4 goes to 1.0 and 1.3 goes to 2.0 etc.

    When a version numbers hits 0.9 and a minor version is added I would like the number to go to 0.10 not 1.0, when I add to it. This is the biggest issue.

    Any suggestions are appreciated.

    Thanks.

  • How can I get all the data types specific for a certain version of MS Access or/and every versions of MS Access?
  • What is the right way to add .NET project with NuGet dependencies to a git repo?
  • How to distribute C++ libraries that depend on other libraries
  • .NET: Large revision numbers in AssemblyVersionAttribute
  • Visual Studio 2015 git Push to Network Drive
  • Which files of an autoconf project to put into .gitignore?
  • 5 Solutions collect form web for “Version Numbers float, decimal or double”

    System.Version

    This already stores the different parts, deals with presenting it as a string (revision and build components are only used in display if they are non-zero, so their irrelevance to your case doesn’t matter) and (best of all) is already understood by other .NET developers, and won’t lead to confusion (if I saw some use of a version number that wasn’t a System.Version I’d spend some time then trying to work out why Version wasn’t good enough for the job, in case that proved important and hid a nasty surprise. If it was good enough for the job, I’d be irritated at the developer wasting my time like that).

    You can deal with the means you want for incrementing easily with extension methods:

    public static Version IncrementMajor(this Version ver)
    {
      return new Version(ver.Major + 1, 0);
    }
    public static Version IncrementMinor(this Version ver)
    {
      return new Version(ver.Major, ver.Minor + 1);
    }
    

    How about two integers? One for major and one for minor revisions?

    Make your own data type for this

    public struct VersionNumber : IComparable<ReleaseNumber>
    {
      public int MajorVersion{get;set;}
      public int MinorVersion{get;set;}
    
      public VersionNumber( int major, int minor)
      {
        MajorVersion = major;
        MinorVersion = minor;
      }
    
      public override string ToString(){
        return major + '.' + minor;
      }
    
      public int CompareTo(VersionNumber other) {
        int result;
        result = MajorVersion.CompareTo(other.MajorVersion);
        if (result != 0) { return result; }
        return MinorVersion.CompareTo(other.MinorVersion);
      }
      public static bool operator <(VersionNumber left, VersionNumber right) {
        return left.CompareTo(right) < 0;
      }
      public static bool operator <=(VersionNumber left, VersionNumber right) {
        return left.CompareTo(right) <= 0;
      }
      public static bool operator >(VersionNumber left, VersionNumber right) {
        return left.CompareTo(right) > 0;
      }
      public static bool operator >=(VersionNumber left, VersionNumber right) {
        return left.CompareTo(right) >= 0;
      }
    }
    

    You can also add a comparer so you can check two version numbers to see which one is the highest version of two version numbers for example.

    EDIT

    Added the comparer logic also for good measure 🙂

    I would suggest two integers: a major and a minor. You can even store this as major * 1000 + minor if you want one variable.

    Decimal should be the best of the above given, but as other has noted two ints would be better.

    Doubles and floats does not accurately store all decimal values, you don’t want your version to suddenly be 1.219999999999999999

    Git Baby is a git and github fan, let's start git clone.