MSBuild Team Blog

This is just what I needed. I was just about to write a custom task myself to set the version number and thought I would do a search just in case this common requirement was already done. Thanks!

P.S. I'll let you know if I find any bugs!

Phil Wright
Free VS2005 GUI Controls...
http://www.componentfactory.com

Nice work. I'm considering changing the version numbering we use in our products, and really like the Visual Studio-style build numbers. (1.0.yyMMdd.revision) However, when I looked into the System.Version class it became obvious that this style will only work for about a year(!)

The problem is that System.Build, .Major, .Minor and .Revision are System.Int32 :(

January 1. 2007 => "1.0.70101.0"
70101 > 65534 => The specified version '1.0.70101.0' is invalid.

(Interestingly the error only occurs if set using the AssemblyVersion attribute. When removing the AssemblyVersion, and only using AssemblyFileVersion, VS is not giving compilation errors, but AssemblyFileVersion("1.0.70101.0")] gives the assembly File Version 1.0.4565.0.0 and Product Version 1.0. 70101.0)

Do you know which build-number-style that will be used on the next version of VS? - Assuming it won't be released next year. :)

Steinar

<Import Project="$(MSBuildExtensionsPath)\Microsoft\AssemblyInfoTask\Microsoft.VersionNumber.targets"/>

This is working perfectly fine with the Projects having AssemblyInfo.cs file.

But how can I update the Version Numbers of the Assemblies generated by the <AspNetCompiler> task for a Website.
All the assemblies generated here show Version as 0.0.0.0

How can I generate the AssemblyInfo.cs file for the Website in advance.

I am using Visual Web Developer and do not have VS 2005.

Please suggest..

Thanks in advance
--Manish

Wait a minute... I don't think there is a Year 2007 problem. Int32 has a max value of 2,147,483,647. I think you are confusing this with UInt16. So turn that frown upside down! :) Because it should work for a million years! We may indeed have a Million year problem though...

-Valkyrie-MT

Steinar said:

The problem is that System.Build, .Major, .Minor and .Revision are System.Int32 :(

January 1. 2007 => "1.0.70101.0"
70101 > 65534 => The specified version '1.0.70101.0' is invalid.

Actually the alt versioning system won't work because of leading zero issue.

Tobias.

Hi

I was wondering if we had resolved the 2007 bug yet or not? (other than changing the formating of build version number)

Jon

hi everybody,
i am new at VS (studying c#) and i eonder that how can i open and COPiLE VS2005 projects withs VS 2003 (on a computer that have not NETFRAMEWORK 2.X  only have 1.1)
maybe some assembly works but i really woder this..
in my school computers dont have  netframework2.x only 1.1. and VS2003 so my projects (created by VS2005) cant be opened in my schools computers..????
:(
maybe you say :MSBuild Toolkit bla bla ..
thanks for now.

[sorry for my bad english-- you are not babysitter so you have not to answer this topic :) ]

I echo Leo's request: will this work on web projects?

I need to charge the custom buiild number so that it contains my local time (Copenhagen) , can i use this to do it

thanks

I can't seem to find the source code on the Microsoft Community License page.   Could you please post the link?

Hello! I want to update version number in AssemblyInfo.cs but I don't want this format: 1.0.yyMMdd.revision. I tried using <Import Project="$(MSBuildExtensionsPath)\Microsoft\AssemblyInfoTask\Microsoft.VersionNumber.targets"/> put in the end of the .csproj file and then, as a test, I tried using command line to execute:

MSBuild.exe <testProject>\Test.csproj /t:Rebuild /p:Assembl

yRevisionType="NoIncrement" /p:AssemblyFileRevisionType="NoIncrement" /p:AssemblyVersion="0.1.38.*" /p:AssemblyFileVersion="0.1.38.*" but in the AssemblyInfo file I got [assembly: AssemblyVersion("1.0.061025.05")] which is not what I want. Can you help me, please?

I'm very proud of Visual Studio Team System and what Microsoft have done here - I've blogged about it

Ok, once I updated these properties in Microsoft.VersionNumber.targets, it works perfect.

Thanks.

Just wondered if any one had come up with a workaround to the 2007 build number issue. I have just tried to build a project 1 Jan 2007 and it threw the error mentioned in the comments above.

I have also come into the office this morning to find that the last two overnight builds have failed with the "2007 problem".

Has anyone made any progress with this problem?

I implemented a new versioning scheme as described in http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1058284&SiteID=1.  It keeps with the spirit of the version numbering scheme but it's far less convenient than yymmdd.  This implementation sets the build number to the 2 digit year followed by the 3 digit day of the year. This scheme will work until 2065 :)

To implement this, follow these steps:

1) Get the AssemblyInfoTask source from http://www.gotdotnet.com/codegallery/releases/viewuploads.aspx?id=93d23e13-c653-4815-9e79-16107919f93e

2) Open AssemblyInfoTask.cs and make the following changes:

   Go to the end of the file and add another entry to the IncrementMethod enum - I used DayOfYear = 3

   Search for "Switch" in the file and add another case for the new increment method.  Copy the DateString case but change the newVersionNumber to be:

string newVersionNumber = DateTime.Now.Year.ToString().Substring(2) + String.Format("{0:000}",DateTime.Now.DayOfYear);

3) Compile the app (remember it needs to be strong named if you want it in the GAC)

4) Install the assembly into the GAC

5) Open <program files>\MSBuild\Microsoft\AssemblyInfoTask\Microsoft.VersionNumber.targets in Notepad - look for the task import (usingTask) and change the PublicKeyToken to match the one from your new assembly.

This seems like the best solution (much better than resetting the year to 1 which is an option I have seen suggested elsewhere).

Are the (strongly named) binaries going to be reposted on GotDotNet?

It seems that

   <AssemblyMajorVersion>1</AssemblyMajorVersion>

   <AssemblyMinorVersion>0</AssemblyMinorVersion>

only work in the targets file, not in the project file. But this file is shared for all projects. How can I set these so they are specific to each project?

Thanks

Danny

Danny,

You can copy the targets file to a local folder and import the local version instead of the one located in MSBuildExtensions. Then each solution or project use a corresponding local copy.

==============

It seems that

  <AssemblyMajorVersion>1</AssemblyMajorVersion>

  <AssemblyMinorVersion>0</AssemblyMinorVersion>

only work in the targets file, not in the project file. But this file is shared for all projects. How can I set these so they are specific to each project?

Thanks

Danny

Seems that godotnet does not exist anymore, but i cannot find the Task on CodePlex either. Where to get it?

I'm really surprised no one has suggested using a year indicator with a Julian day of year instead of the month/day.  This would save one digit and get us past this issue.

There were over 80 responses to my recent post asking for feedback on where MSBuild should be heading

When searching the URL http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=5C455590-332C-433B-A648-E368B9515580 , i received the message

"The GotDotNet site has been shut down". I tried to search the new site, but was unable due to security restrictions at my enterprise. Please, could anyone post the new site for the URL above? Thanks.

Ok. while YYDDD is convinient. i really dont want to download the source file and modify them. personal reasons and just want to see a clear yymmdd in there.

instead i used

major.minorYY.MMDD.Revisions

since i manually input the minor revisions.

might as well edit it yearly

so i formated it in my project as

minorYY

sample

1.108.0319.05

major -1

minor -1 (with year 08)

build - mmdd

revision - auto increment

This seems to be the new URL:

http://www.codeplex.com/tfsbuildversionsync

Hi,

I am facing a problem using AssemblyTaskInfo in my Subversion source Control. After adding IMPORTS line to my project file, I am continuously getting UNAUTHORIZED ACCESS (ACCESS DENIED to \SVN\txt-bases\Assembly***.cs file)

Have you seen this error before? Any workaround?