As you probably have noticed there have been no new posts, in english, for a while. Do not worry, i’m not dead 
Right now my time is taken up by other occupations:
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.
Carpe Diem.
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!
Carpe Diem.
After showing you how to customize IntelliTrace, i’ll show you today how you can create your own graph dependency analyzers for VisualStudio 2010 architecture tools.
Before starting here is another warning (still in bold and red so everyone sees it ):
Microsoft does not give any documentation or support on all that i will explain because even it’s possible, the functionality is not supported.
Now that you are warned lets start implementing a small analyzer which will show us all nodes starting with “Qetza.”.
First we create a class library and add the following assembly references:
These assemblies are in the sub directory “Common7\IDE\PrivateAssemblies” of your VisualStudio 2010 install directory (by default “C:\Program Files\Microsoft Visual Studio 10.0″).
I’ve published on codeplex a small command-line tool to administer work item queries: wiqadmin.
This tools, compatible with TFS 2008 and TFS 2010, supports the following commands:
The TFS 2010 version supports folders
Carpe Diem.
This post is part of a series on TeamBuild 2010:
It’s time i get back to my presentation of TeamBuild 2010 new features
Since TeamBuild is now based on Workflow Foundation 4.0 Microsoft has provided some activities specifically for TeamBuild. Those activities are like the Task in TeamBuild 2008 :
Today i’ll show you how to customize IntelliTrace in VisualStudio 2010 so that you can trace events from your own methods. But first some warnings (in bold and red so no one misses them ):
Microsoft does not give any documentation or support on all that i will explain. There is also a chance that the way you can customize IntelliTrace will be revamp in the next version of VisualStudio (which might explain the lack of documentation and support).
Now that you’re warned let start and see how we can customize IntellTrace so that we can trace our own method calls! I’ll be using the following class for this post:
I finally installed the WordPress plug-in ZdMultilang to make my blog multilingual. There is no more FR and EN tag to differentiate posts. Here are the new functionalities:
To access my blog in English : http://blog.qetza.net/en/
The English feed url : http://blog.qetza.net/en/feed/
I’ve added permanent redirection on previous English posts to the new ones.
Carpe Diem
This post is part of a series on TeamBuild 2010:
What is a “Gated Check-in”? It’s a new type of build which is launched automatically every time a developer makes a check-in. But unlike continuous integration, a “Gated Check-in” will reject the check-in if the build is on error.
Technically, the “Gated Check-in” uses shelvesets. When a developer makes a check-i, Visual Studio will prompt him with a new dialog asking to shelve it’s modifications: