A good option to customize TFS2010 build workflow is creating a Custom Activity, an operation that is quite different from creating a Custom Code Activity. A custom activity does not contain any code at all and it is only composed by sub activities. This kind of customization is really useful to create pieces of workflow that will be inserted in main build workflow. As an example I created a simple custom activity to deploy a database project on a custom Database Server.
The overall operation was already covered in this post, but as you can see that technique involved a MsBuild Activity and you needed to specify values with a really bad â€œcommand line parameterâ€ syntax.
Specifying parameter with this technique is awkward and error prone. To solve this situation you can simply create a custom activity. Once you created it, you need to go to â€œArgumentsâ€ tab and insert all the input and output parameters you need.
With this approach, you can use default value for arguments, and you can specify the exact type for arguments, so the workflow can do type checking against the input arguments. Iâ€™ve inserted all the input parameters I need: database name, server name, dbProjectname etc etc. Inside the Activity I simply drop a sequence and inside the sequence all the actions needed to deploy the database. The exact technique is described in my old post, the only remarkable difference is logging, because now I can directly drop a WriteBuildMessage activity inside the sequence to log messages. Here is the final activity
Once you have compiled this, you can insert in the build workflow. The great advantage of this approach is that you are now able to specify parameters with great easy.
Compare this with the original approach, where you needed to insert the string
" /p:""DefaultDataPath=C:Program FilesMicrosoft SQL ServerMSSQL10.SQL2008MSSQLDATA""" +
" /p:""TargetConnectionString=Data Source=10.0.0.99SQL2008,49400%3Buser=sa%3Bpwd=Pa$$w0rd""" +
Directly inside the CommandLineArgument of MsBuild activity. Now each parameter can be specified alone, and the whole action is much more readable.
Clearly the output result is exactly the same as before, because under the hood it is composed by exactly the same sequence of actions, but now they are all wrapped inside a single Activity, making the workflow more readable.
Tags: Team Foundation Server