|Number of votes:||2|
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: http://world.episerver.com/download/Items/EPiServer-Commerce/episerver-commerce-8-tools-and-code-samples/
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.