Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. C#
  4. AssemblyInfo Version Number

AssemblyInfo Version Number

Scheduled Pinned Locked Moved C#
questiondiscussionannouncement
8 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    David Muir
    wrote on last edited by
    #1

    Hi All, I am currently trying to figure out how the [assembly: AssemblyVersion("1.0.0.*")] works. In particular the * part of it. I understand about the Major Number, Minor Number and Build Number. What I don't understand is the Revision Number. As it is * it automatically increments... however; what determines the revision number. I.e. where does it come from? If anyone knows, I'd appreciate your thoughts, Thanks :)

    S G 2 Replies Last reply
    0
    • D David Muir

      Hi All, I am currently trying to figure out how the [assembly: AssemblyVersion("1.0.0.*")] works. In particular the * part of it. I understand about the Major Number, Minor Number and Build Number. What I don't understand is the Revision Number. As it is * it automatically increments... however; what determines the revision number. I.e. where does it come from? If anyone knows, I'd appreciate your thoughts, Thanks :)

      S Offline
      S Offline
      Shyam K Pananghat
      wrote on last edited by
      #2

      It is nothing but the number of Build action. I suppose.

      Shyam.. My Blog dotnetscoups.blogspot.com

      D 1 Reply Last reply
      0
      • S Shyam K Pananghat

        It is nothing but the number of Build action. I suppose.

        Shyam.. My Blog dotnetscoups.blogspot.com

        D Offline
        D Offline
        David Muir
        wrote on last edited by
        #3

        This is also what i expected... however; I dont understand how it is generated. For example, the application i am currently working on requires it to be displayed. I ran the appplication and the number that was displayed was 1.2.0.19976, I made a couple of changes and ran it again, then the new version number was 1.2.0.20068. I don't understand why it increments so much. :)

        S 1 Reply Last reply
        0
        • D David Muir

          This is also what i expected... however; I dont understand how it is generated. For example, the application i am currently working on requires it to be displayed. I ran the appplication and the number that was displayed was 1.2.0.19976, I made a couple of changes and ran it again, then the new version number was 1.2.0.20068. I don't understand why it increments so much. :)

          S Offline
          S Offline
          Shyam K Pananghat
          wrote on last edited by
          #4

          Check how many time you hit F5, Build , Rebuild or Batch Build between the first and second run.

          Shyam.. My Blog dotnetscoups.blogspot.com

          D 1 Reply Last reply
          0
          • D David Muir

            Hi All, I am currently trying to figure out how the [assembly: AssemblyVersion("1.0.0.*")] works. In particular the * part of it. I understand about the Major Number, Minor Number and Build Number. What I don't understand is the Revision Number. As it is * it automatically increments... however; what determines the revision number. I.e. where does it come from? If anyone knows, I'd appreciate your thoughts, Thanks :)

            G Offline
            G Offline
            Giorgi Dalakishvili
            wrote on last edited by
            #5

            Have a look at AssemblyVersion build and revision number[^]

            Giorgi Dalakishvili #region signature My Articles Asynchronous Registry Notification Using Strongly-typed WMI Classes in .NET [^] My blog #endregion

            S 1 Reply Last reply
            0
            • S Shyam K Pananghat

              Check how many time you hit F5, Build , Rebuild or Batch Build between the first and second run.

              Shyam.. My Blog dotnetscoups.blogspot.com

              D Offline
              D Offline
              David Muir
              wrote on last edited by
              #6

              It seems that the revision number is the number of seconds since midnight divided by 2 :) http://msdn.microsoft.com/en-us/library/system.reflection.assemblyversionattribute.assemblyversionattribute(vs.71).aspx[^]

              1 Reply Last reply
              0
              • G Giorgi Dalakishvili

                Have a look at AssemblyVersion build and revision number[^]

                Giorgi Dalakishvili #region signature My Articles Asynchronous Registry Notification Using Strongly-typed WMI Classes in .NET [^] My blog #endregion

                S Offline
                S Offline
                Shyam K Pananghat
                wrote on last edited by
                #7

                oh.. Great.. Thanks Giorgi :)

                Shyam.. My Blog dotnetscoups.blogspot.com

                G 1 Reply Last reply
                0
                • S Shyam K Pananghat

                  oh.. Great.. Thanks Giorgi :)

                  Shyam.. My Blog dotnetscoups.blogspot.com

                  G Offline
                  G Offline
                  Giorgi Dalakishvili
                  wrote on last edited by
                  #8

                  You are welcome :)

                  Giorgi Dalakishvili #region signature My Articles Asynchronous Registry Notification Using Strongly-typed WMI Classes in .NET [^] My blog #endregion

                  1 Reply Last reply
                  0
                  Reply
                  • Reply as topic
                  Log in to reply
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes


                  • Login

                  • Don't have an account? Register

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • World
                  • Users
                  • Groups