Team…
Wondering if anyone has some insight on this…
I created a custom workflow activity to gather client records and move those list items and documents to another list and library (respectively).
The control is currently working fine on production on the SP2010 server.
The problem is that I have been working through the client’s customizations on their new SP2013 farm and this custom activity will not work.
I have followed this URL which describes the exact problem I have, but it still will not work.
I have redeployed the custom activity wsp multiple times, removing first and then redeploying.
The %windir%\assembly list shows the library there.
SharePoint Designer 2013 shows my custom action in the actions list when I create new workflows.
The entry in the web.config authorizedtypes is there as it is on the functioning production SP2010 environment with the exception of the new sub level of <targetFx version=”v4.0″>
I have been banging my head against this one for a full day. Arrrrrrrrrrgh!
One thing that has puzzled me is that the “targetFx” version is “v4.0″ and the custom library is actually .Net 3.5. Should I recompile under 4.0 or possibly add a section for <targetFx version=”v3.5”>?
Thoughts?
Wow… I don’t believe it… I swear I didn’t do anything new with the exception of trying to use the targetFx version = 3.5 section under authorized types in the web.config file (under the appropriate c:\inetpub location).
I restarted IIS using an IISRESET and the server did exactly the same thing. So, I switch the authorizedType entry back to the documented location (under targetFx version=4.0) and again, did an iisreset.
Then, it worked. This is after probably 6 hours of researching. Nuts.
