Views: 2610
Number of votes: 2
Average rating:

Building your custom Commerce workflow project

Recently we released EPiServer Commerce 8.7.1, with many updates, and the most important thing is to update our workflows to take advantages of new inventory system, and, to merge the two projects – Mediachase.Commerce.Workflow and Mediachase.Commerce.Workflow.Activities into one. The reason? To help simplifying the steps you need to build your customer workflow project. The project source code can be found here:

So if you have custom workflow project, you will need to rebuild it to apply new chances from our workflows. A few notes that might save you some headaches:

- You only need to install EPiServer.Commere.Core to your workflow project. Remove reference to old Mediachase.Commerce.Workflow.Actitivies.dll. If you are customizing by using our project (Build to Mediachase.Commerce.Workflow.dll), make sure to remove the reference to itself. This has been noted in our release notes.

- If you use activities from Mediachase.Commerce.Workflow.Activities in your own workflows, make sure to update namespaces to use Assembly=Mediachase.Commerce.Workflow (remove “.Activities” part).

- EPiServer Commerce 8.7.1 was built with EPiServer.CMS.Core 7.19.1. Build your workflow project before upgrading to later version of CMS/Framework (7.19.2, for example). The reason was to build workflows, Visual Studio will use msbuild and call to Microsoft’s WorkflowCompilation target, which does not care about the assembly binding redirects (defined in web.config or app.config). It cannot load EPiServer.Business.Commerce.dll 7.19.1 because it can’t load EPiServer.Framework.dll 7.19.1, and will throw a very cryptic message: "Compilation failed. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information."

Then you can build your custom project and experience interesting features of our new inventory service system.

Feb 09, 2015

Arve Systad
( By Arve Systad, 2/9/2015 11:43:15 AM)

I spent nearly a whole day struggling with this.

Future updates should be such that stuff released at the same time (typically the same "Update XX" patch) should be built all with the same, newest versions. If workflows can't be built with the newest CMS-version, it should be re-released with the same dependencies as the newest CMS-version. So in effect: "Update all" should be possible to do on the EPiServer nugets at any time without breaking the build (unless there are breaking changes to the APIs of course, which would be the exception).

K Khan
( By K Khan, 2/9/2015 3:38:41 PM)

+1 for Arve suggestion

( By GOSSO, 2/13/2015 1:56:09 PM)

I finaly got my workflow-project working in CMS 7.19.2. What i did was to download 7.19.1 separatly, and referenced my workflow project to these DLLs. Anyhow this is not desirable approach. I wonder what will happen on next update.

( By GOSSO, 2/13/2015 2:05:14 PM)

It seems that i have a similar error in commerce manager now. I did upgrade Mediachase.ConsoleManagerUpdate.sln thru PackageManagerConsole in VS2013 and when running Commerce manager i do get "Could not load file or assembly 'EpiServer.Implementatio, Version 7.19.1' or one of its dependencies". Even thought i have assembly bindings redirects to 7.19.2 in web.config in the commerce folder. How come? is it related?

( By GOSSO, 2/16/2015 2:27:46 PM)

Regarding Mediachase.ConsoleManagerUpdate. I did downgrad to 7.19.1 and it works. what does that mean --> never use Update-Package to the latest version? how should we know that "EPiServer Commerce 8.7.1 was built with EPiServer.CMS.Core 7.19.1."??

Please login to comment.