For the Build Process in TFS 2010 I\'ve created a library containing some custom code activities. In the past it all worked fine by adding the library (*.dll) to Source Con
This solution might not apply to all cases, as the answers provided in previous posts are correct, but were not the solution to my issue. This answer assumes the following:
What I and(I suspect many others) are doing is copying, or linking their xaml workflow documents into the solution so you can use the workflow designer and the new custom assemblies. Well, this works great in the VS designer, but VS will modify your assembly references with its own. For example I have a reference that looks like the following:
xmlns:ca="clr-namespace:Custom.TFS.Activities;assembly=Custom.TFS.Activities"
After editing the workflow with my project solution, visual studio changed that to:
xmlns:local="clr-namespace:Custom.TFS.Activities"
When you check this file in to test or use, you will now see the dreaded TF215097 error.
Adding the ;assembly=your.assembly should fix the problem and remove the need to put everything in the GAC. You might also need to fix the name space references using in the rest of the xaml file.
BIG THANKS TO: http://msmvps.com/blogs/rfennell/archive/2010/03/08/lessons-learnt-building-a-custom-activity-to-run-typemock-isolator-in-vs2010-team-build.aspx