Yes according to this Blog.
Else, you could use MSBuild 4.0 to do so :
Or, here is a GREAT example to extend the workflow floundation :
"Version Assemblies with TFS 2010 Continuous Integration", using Custom Workflow Activity :
In all cases, a good idea is to rely on CodePlex, such as an MSBuild Extension to ease your life:
As a general guidance (Jim Lamb, build automation features) :
· If the task requires knowledge of specific build inputs or outputs, use MSBuild
· If the task is something you need to happen when you build in Visual Studio, use MSBuild
· If the task is something you only need to happen when you build on the build server, use WF unless it requires knowledge of specifi build inputs/outputs
When using MSBuild, remember that you can customize your project files directly (by unloading them and then editing them in Visual Studio), or you can create custom .targets files and import them into your individual projects. The latter approach is useful for functionality that's common to multiple projects to avoid maintaining multiple copies.
When using WF, remember that you can write code activities for low-level tasks but that you can also compose higher-level tasks using straight XAML. We're actually working on a version of the default build process template that shipped with TFS 2010 that gives you a simpler, less granular view of the overall process by using a set of composed XAML activities.