Your feedback and suggestions are welcomed, use the site’s forum for this
We intend to continue on a release every 2 or 3 months. Your feedback and suggestions are welcomed, use the site’s forum for this
Yesterday was released the first stable version of the Community TFS Build Extensions. It’s a set of new activities for TeamBuild 2010 so that you can customize your build process. Here are some of the provided activites:
A big thanks to Mike Fourie the coordinator and principal contributor on the projet and to all other contributors (including me :)).
We welcome your feedback and suggestions. It’s a start and we hope to release new versions every 2 or 3 months.
Here’s a small post on how to add customized expandable parameters to a build workflow. What i mean by expandable parameters is parameters with a small + sign so that you can expand the parameter to fill its properties, the main line containing a summary of the values:
I published the version 1.1 of my TeamBuild 2010 activity to update versioning attributes in AssemblyInfo files. This new version brings the following features:
As promized her is a sample of how i’m using the UpdateAssemblyInfo activity i’ve published on codeplex.
First let’s describe what we want:
Before updating our build template i’ll start by configuring my solution to make easier the versionning of all the projects. Let’s add a GlobalAssemblyInfo.cs (or .vb if you use VB.Net) file to the solution as a solution item:
Brian Harry just annouced on his blog that the Developer Division has made successfully it’s first end-to-end build of all Visual Studio using TeamBuild 2010. Here’s an other proof that it’s a great product.
As Brian says, Microsoft will now be able to test and find missing features to add for future versions.
I’ve published on codeplex an activity which provides a way to manipulate the AssemblyVersion and AssemblyFileVersion values of AssemblyInfo files at build time under TeamBuild 2010: UpdateAssemblyInfo.
This activity supports the use of a pattern to specify how to update the AssemblyInfo files versions. the following tokens are dynamically replaced during execution:
The specified pattern must respect the version numbers form “A.B.C.D”. As an example, the pattern “$(current).$(current).$(increment).0″ keeps the current major and minor version, increments the build number and forces the revision to 0.
I’ll post an entry on an example of how to integrate this activity soon but for now i’ll recover for those past days heat (and the lack of sleep which goes with it :)). Stay tuned!