Comments on: AssemblyVersion - BuildNo Limitation http://michaelsync.net/2007/01/12/assemblyversion-buildno-limitation Sharing our knowledge Fri, 08 Aug 2008 21:00:37 +0000 http://wordpress.org/?v=2.6 By: 0205 http://michaelsync.net/2007/01/12/assemblyversion-buildno-limitation#comment-1812 0205 Sun, 07 Oct 2007 09:03:29 +0000 http://michaelsync.net/2007/01/12/assemblyversion-buildno-limitation#comment-1812 <strong>0205</strong> Free Flash gamesz online Visit www.Flashgamesz.net 0205

Free Flash gamesz online Visit http://www.Flashgamesz.net

]]> By: mUnit : Mun talks technology » Assembly Version Numbers and .NET http://michaelsync.net/2007/01/12/assemblyversion-buildno-limitation#comment-1802 mUnit : Mun talks technology » Assembly Version Numbers and .NET Sat, 17 Feb 2007 22:02:29 +0000 http://michaelsync.net/2007/01/12/assemblyversion-buildno-limitation#comment-1802 [...] I came across Michael Sync’s blog, where he also experienced this problem and wrote about his findings.  In summary, he [...] [...] I came across Michael Sync’s blog, where he also experienced this problem and wrote about his findings.  In summary, he [...]

]]> By: Ashish C. http://michaelsync.net/2007/01/12/assemblyversion-buildno-limitation#comment-1800 Ashish C. Wed, 17 Jan 2007 11:18:35 +0000 http://michaelsync.net/2007/01/12/assemblyversion-buildno-limitation#comment-1800 Remember if you grow tired of programming you could of course freeze yourself anf go to 9999! :P I'll skip the post since it goes over my head! Remember if you grow tired of programming you could of course freeze yourself anf go to 9999! :P
I’ll skip the post since it goes over my head!

]]> By: Alex Espinoza http://michaelsync.net/2007/01/12/assemblyversion-buildno-limitation#comment-1801 Alex Espinoza Tue, 16 Jan 2007 21:25:25 +0000 http://michaelsync.net/2007/01/12/assemblyversion-buildno-limitation#comment-1801 The thing is the actual add-in doesn't follow the rules it says it does. The first thing is that this plug in uses the reference date 1/1/2000 00:00:00. AA & BB are used my project. So it is Major version 1, and minor version 1. CC=25 & DD=68 are seen as 2568 days since the reference date (1/1/2000). EE=400 & FF=48 are seen as 40048 seconds. But this is interesting, remeber the 65534 limit for build numbers? well 40048 seconds is actually 80096, but since that number is too big, the developer of the add-in cuts the seconds in half. revisionVersion = (int)(currentDateTime.TimeOfDay.TotalSeconds / 2); Another really interesting thing, is that the plug in uses Utc time. The thing is the actual add-in doesn’t follow the rules it says it does.

The first thing is that this plug in uses the reference date 1/1/2000 00:00:00.

AA & BB are used my project. So it is Major version 1, and minor version 1.

CC=25 & DD=68 are seen as 2568 days since the reference date (1/1/2000).

EE=400 & FF=48 are seen as 40048 seconds. But this is interesting, remeber the 65534 limit for build numbers? well 40048 seconds is actually 80096, but since that number is too big, the developer of the add-in cuts the seconds in half.

revisionVersion = (int)(currentDateTime.TimeOfDay.TotalSeconds / 2);

Another really interesting thing, is that the plug in uses Utc time.

]]> By: Michael Sync http://michaelsync.net/2007/01/12/assemblyversion-buildno-limitation#comment-1803 Michael Sync Sat, 13 Jan 2007 13:35:54 +0000 http://michaelsync.net/2007/01/12/assemblyversion-buildno-limitation#comment-1803 Thanks so much. Alex. <blockquote> This article "Build Number Automation for Visual Studio .NET Projects By Darrel Liu" AA.BB.CCDD.EEFF AA is the major version BB is the minor version CC will be used to represent the number of months elapsed since the starting of the project, DD the number of days after those months. EE and FF will be the hours and minutes the build was created in that day. for example, if the project started on Jan 10, 2003 with version 1.0 and you run this macro on Mar 15, 2003 at 14:00, this is the build number that comes out of the calculation: 1.0.0205.1400. </blockquote> Is it the way that you are using?? If so, I'm not sure why you got this no "1.1.2568.40048" for today?? AA = 1 BB = 1 CC = 25 DD = 68 EE = 400 FF = 48 Thanks so much. Alex.

This article “Build Number Automation for Visual Studio .NET Projects By Darrel Liu”

AA.BB.CCDD.EEFF

AA is the major version
BB is the minor version
CC will be used to represent the number of months elapsed since the starting of the project,
DD the number of days after those months.
EE and FF will be the hours and minutes the build was created in that day.

for example,
if the project started on Jan 10, 2003 with version 1.0 and you run this macro on Mar 15, 2003 at 14:00, this is the build number that comes out of the calculation: 1.0.0205.1400.

Is it the way that you are using??
If so, I’m not sure why you got this no “1.1.2568.40048″ for today??

AA = 1
BB = 1
CC = 25
DD = 68
EE = 400
FF = 48

]]> By: Alex Espinoza http://michaelsync.net/2007/01/12/assemblyversion-buildno-limitation#comment-1804 Alex Espinoza Fri, 12 Jan 2007 22:17:12 +0000 http://michaelsync.net/2007/01/12/assemblyversion-buildno-limitation#comment-1804 This is really interesting. I also thought you could use whatever numbers you would like. I'm currently using <a href="http://www.codeproject.com/dotnet/VersioningControlledBuild.asp" rel="nofollow">VCB</a> add-in to manage my build versions. I'm actually using the Microsoft scheme which uses the date and hour. For today I got: 1.1.2568.40048 It is some kind of Date&Time scheme. You should try this tool. It rocks. This is really interesting. I also thought you could use whatever numbers you would like.

I’m currently using VCB add-in to manage my build versions. I’m actually using the Microsoft scheme which uses the date and hour. For today I got: 1.1.2568.40048

It is some kind of Date&Time scheme. You should try this tool. It rocks.

]]>