After creating a custom Workflow 4 activity, I was planning to add it to our existing build process template. However after adding the activity to the toolbox in Visual Studio, I couldn’t drop the activity on the workflow designer.
The reason is that the workflow designer is not able to find the assembly containing the custom activity. There are multiple solutions out there to solve this problem. Probably the easiest one is adding the assembly to the GAC. Two other alternatives are:
- Adding the process template to a project and reference the assembly from this project.
- Adding the assembly to a location where Visual Studio will find it (e.g. ..\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\PublicAssemblies).
If you want to know more about customizing the build process template, I can recommend the following blog series by Ewald Hofman:
- Part 1: Introduction
- Part 2: Add arguments and variables
- Part 3: Use more complex arguments
- Part 4: Create your own activity
- Part 5: Increase AssemblyVersion
- Part 6: Use custom type for an argument
- Part 7: How is the custom assembly found
- Part 8: Send information to the build log
- Part 9: Impersonate activities (run under other credentials)
- Part 10: Include Version Number in the Build Number
- Part 11: Speed up opening my build process template
- Part 12: How to debug my custom activities
- Part 13: Get control over the Build Output
- Part 14: Execute a PowerShell script
- Part 15: Fail a build based on the exit code of a console application