I'm migrating a solution from MOSS2007 to SharePoint 2010.
I have, among others, custom workflow actions in a DLL deployed to the GAC (e.g. MyWorkflows.dll version 184.108.40.206).
My new solution contains new workflow actions that target the SharePoint 2010 API (e.g. MyWorkflows.dll version 220.127.116.11).
So what I'm doing is:
- Creating a workflow in SPD in a MOSS2007 environment. Such workflow contains one of my custom actions.
- Upgrading the environment to SharePoint 2010.
- Removing the WSP package containing my files/DLLs that targeted MOSS2007 and deploying a new WSP containing the solution files that target SharePoint 2010.
- Add assembly redirection entries in the web.config file of my web application, so that calls to MyWorkflows.dll 18.104.22.168 get redirected to MyWorkflows.dll version 22.214.171.124 (I also add other redirection entries regarding other stuff - for example, webparts).
- Reset IIS and OWSTIMER.
After that I can see that the old webparts work fine (the assembly redirection seems to work for them). However, when I try to run a workflow (manually, from the browser) it doesn't work. I get the following error in the ULS log:
Microsoft.SharePoint.SPException: <Error><CompilerError Line="15" Column="3" Text="Could not deserialize object. The type 'MyWorkflows.MyActivity' could not be resolved." /></Error> &nbs
View Complete Post