gerbenvl

Can anyone give any samples or directions on how to use the AssemblyInfo task with Team Build when the teambuild is building two solutions I'd like to have different version numbers for each solution.

This one: http://blogs.msdn.com/gautamg/archive/2006/01/04/509146.aspx is only using one solution.

Thanks,

Gerben.



Re: Team Foundation Server - Build Automation AssemblyInfo task with two solutions

Aaron Hallberg - MSFT

Your simplest bet here would be:
  1. Leaving the Exec portions of the target overrides in your TfsBuild.proj file, and
  2. Moving the <Import> of Microsoft.VersionNumber.targets and the Assembly* property declarations into your individual project files (i.e. your *.csproj files, *.vbproj files, and so forth).
The solution in Gautam's blog relies on the Microsoft.VersionNumber.targets overriding the Team Build CoreCompileDependsOn property, thus adding the version number logic to the team build build process. Taking the above approach would make the Microsoft.VersionNumber.targets override the individual project CoreCompileDependsOn properties, thus adding the version number logic to the standard C# / VB / etc. project-level build process. Keeping the Exec portions of the logic around will preserve the checking out (and back in) of the various AssemblyInfo.cs files, however.

Hope this helps get you started,
Aaron





Re: Team Foundation Server - Build Automation AssemblyInfo task with two solutions

gerbenvl

Thanks,

I'll give it a try.

Gerben.