If you use NServiceBus' Configure.With fluent interface, and you use Code Contracts in any assem­blies that your NServiceBus config­u­ration uses, then configure Code Contracts in those assem­blies not to build separate code contract assem­blies, because this confuses NServiceBus.

Configure.With scans all assem­blies for imple­men­ta­tions, and if any imple­men­tation you have also generates code contract assem­blies, then basi­cally you will end up with 2 assem­blies that expose the same classes — one with the actual imple­men­tation, the other with the code contracts. This confuses NServiceBus and you'll get an error:

There is a component already registered for the given key

The simple solution is to go to the "offending" assembly project's Properties, select the Code Contracts tab, and in the Contract Reference Assembly drop­downlist, select "(none)" instead of "Build". The contract code will then be compiled straight into the code assembly rather than sepa­rately, and this will fix the issue with NServiceBus.

The Team Foundation Server team has just released the first beta of an all-​​new Scrum template for TFS 2010. This template competes with MSF Agile 5 up to some point, but more specif­i­cally it competes with EMC2's Scrum for Team System v3.

My first impression is that the new Scrum template is indeed a much better match for Scrum than MSF Agile 5, which was also targeted towards Scrum teams. It seems a simpler imple­men­tation than EMC2's (formerly Conchango's) template. Both are free.

Right now I am using EMC2's template on a project, and my client is about to roll out TFS 2010 on a larger scale, so for me the timing is just right. The next few weeks, we'll have a look at the new template and decide what to use for the next batch of projects.

It will be inter­esting to see whether Scrum teams every­where will adopt the more powerful Scrum for Team System v3 or will prefer the simpler, but less powerful, "standard" Microsoft imple­men­tation. Time will tell. I'd be most inter­ested to hear from you what you prefer, and why.