Dot net assembly versioning

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Coder
    #1

    Dot net assembly versioning

    I notice that MS says the version numbers have the following format:
    <major version>.<minor version>.<build number>.<revisi on>

    If you give a assembly version as "1.0.*", the two latest numbers should
    increment.

    However, the latest number (rightmost/revision) is the fastest moving, which
    increments for every build. Shouldn't that be the Build no, not the
    revision no ?

    And when does the 3rd number (now called build number, but shouldn't it be
    the revision no) increments ?

    Anybody know anything ?



    best regards

    Terje




    Tags: qfe versionminor
    • Mickey Williams
      #2
      Re: Dot net assembly versioning

      In some of the older documentation, the revision portion was called the QFE,
      which was clearer (I think). Its semantics are that an incrementing value
      indicates a non-breaking change.

      Today the reality is that generally people that don't use strong names
      accept the default behavior for the last two segments, which is:
      - the third segment is incremented every day (from 1/1/2000)
      - the fourth segment is incremented every two seconds (from midnight)

      --
      Mickey Williams
      Author, "Microsoft Visual C# .NET Core Reference", MS Press
      servergeek.com
      https://www.servergeek.com



      "Coder" <ts@nospamwante d.osiris.no> wrote in message
      news:eXfjIPsqDH A.3732@tk2msftn gp13.phx.gbl...[color=blue]
      > I notice that MS says the version numbers have the following format:
      > <major version>.<minor version>.<build number>.<revisi on>
      >
      > If you give a assembly version as "1.0.*", the two latest numbers should
      > increment.
      >
      > However, the latest number (rightmost/revision) is the fastest moving,[/color]
      which[color=blue]
      > increments for every build. Shouldn't that be the Build no, not the
      > revision no ?
      >
      > And when does the 3rd number (now called build number, but shouldn't it be
      > the revision no) increments ?
      >
      > Anybody know anything ?
      >
      >
      >
      > best regards
      >
      > Terje
      >
      >
      >
      >[/color]


        Comment

        • Eric Newton
          #3
          Re: Dot net assembly versioning

          Another note:
          C# and VB.Net's "auto incrementing" have different incrementing formulas...

          --
          Eric Newton
          C#/ASP Application Developer
          eric@cc.ensoft-software.com [remove the first "CC."]

          "Mickey Williams" <my first name at servergeek.com> wrote in message
          news:%23LSwAysq DHA.2012@TK2MSF TNGP12.phx.gbl. ..[color=blue]
          > In some of the older documentation, the revision portion was called the[/color]
          QFE,[color=blue]
          > which was clearer (I think). Its semantics are that an incrementing value
          > indicates a non-breaking change.
          >
          > Today the reality is that generally people that don't use strong names
          > accept the default behavior for the last two segments, which is:
          > - the third segment is incremented every day (from 1/1/2000)
          > - the fourth segment is incremented every two seconds (from midnight)
          >
          > --
          > Mickey Williams
          > Author, "Microsoft Visual C# .NET Core Reference", MS Press
          > www.servergeek.com
          >
          >
          > "Coder" <ts@nospamwante d.osiris.no> wrote in message
          > news:eXfjIPsqDH A.3732@tk2msftn gp13.phx.gbl...[color=green]
          > > I notice that MS says the version numbers have the following format:
          > > <major version>.<minor version>.<build number>.<revisi on>
          > >
          > > If you give a assembly version as "1.0.*", the two latest numbers should
          > > increment.
          > >
          > > However, the latest number (rightmost/revision) is the fastest moving,[/color]
          > which[color=green]
          > > increments for every build. Shouldn't that be the Build no, not the
          > > revision no ?
          > >
          > > And when does the 3rd number (now called build number, but shouldn't it[/color][/color]
          be[color=blue][color=green]
          > > the revision no) increments ?
          > >
          > > Anybody know anything ?
          > >
          > >
          > >
          > > best regards
          > >
          > > Terje
          > >
          > >
          > >
          > >[/color]
          >
          >[/color]


            Comment

            • Grant Richins [MS]
              #4
              Re: Dot net assembly versioning

              "Eric Newton" <eric@cc.enso ft-software.com> wrote in message
              news:O9yl6BvqDH A.372@TK2MSFTNG P11.phx.gbl...[color=blue]
              > Another note:
              > C# and VB.Net's "auto incrementing" have different incrementing[/color]
              formulas...[color=blue]
              >
              > --
              > Eric Newton
              > C#/ASP Application Developer
              > eric@cc.ensoft-software.com [remove the first "CC."][/color]


              I would like proof of that because they both call the same DLL (alink.dll)
              to do the auto-incrementing.

              --
              --Grant
              This posting is provided "AS IS" with no warranties, and confers no rights.



                Comment

                Previous template Next
                Working...