- Create a strongly-named / signed VS project for the Activity(s) separately from the Workflow project in which said Activity(s) would be used.
- Deploy the activity project's .dll to the GAC before deploying the Workflow, in my case via the build script:
"C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" /i "
Wednesday, July 16, 2008
In addition to steps that books and tutorials everywhere will tell you, I found I had to take two extra steps to incorporate a custom activity in a custom workflow built in VS 2008: