Upgrade iLoveSharePoint Workflow actions for SPD to 2013

After test upgrading my Project Portal, I was not able to edit the custom workflow I had built in SPD using the iLoveSharePoint Workflow action from Codeplex (which is awesome btw).

I struggled a bit with this today but finally found the perfect solution if you want to upgrade this workflow action for SharePoint 2013. I use this workflow action to automate the creation of project sites at our company intranet and find it very useful.

So first start with adding and installing the wsp file again on the SP 2013 server:

Add-SPSolution d:xxx.wsp (where ever you store the wsp file)
Install-SPSolution iLoveSharePoint.Workflow.Activities.wsp -GACDeployment -CompatibilityLevel {14, 15}

Then you need to also edit the web.config file (and I have had to do this for all my custom wsp files) and move this section:

into the “targetFx” section:

I did an IISRESET right after, and then made sure it got deployed in “Farm solutions” in CA.

When you open the workflow in SharePoint Designer 2010, this is what it should look like:

But when you open it in SPDF 2013 you will have to add back the custom actions, they are gone of course. So add back the custom actions, make sure the workflow looks like it should and publish it again to your site:

Share this blog post:

Leave a Reply

6 Comment threads
0 Thread replies
Most reacted comment
Hottest comment thread
2 Comment authors
divyaJeremy BennettAnonymousLise Rasmussen Recent comment authors

This site uses Akismet to reduce spam. Learn how your comment data is processed.

newest oldest most voted
Notify of

where can i get ilovesharepoint.workflow.activities.wsp file can yu help me out finding this

Lise Rasmussen

Hi Anonymous! Glad to hear that! The web.config you always find in c:inetpubwwwrootwssvirtualdirectoriesportnumberofyourwebapp


Thanks. This article is the only reason I was able to install on our SharePoint 2013 on Prem 🙂

Where is the web.config file?

Lise Rasmussen

Haha!! Thanks Jeremy 😉

Jeremy Bennett

I had to explicitly point to c:tempILoveSPBabe.wsp to get that error message to go away