Hi,
This is a known issue, related to Msbuild target for workflow. You'll need to revert back to previous version of EPiServer Framework, instead of 8.3. In other words: update EPiServer.Commerce only, do not update EPiServer.CMS.Core/EPiServer.Framework manually.
Regards.
/Q
Hi,
Is this something you guys are working on? It is important that I can keep the system up-to-date and that I can keep my references consistent.
Hi
We have plans to remove dependencies on Windows Workflow Foundation on upcoming major release - possibly Commerce 9. Right now this is something we have to live with - to stay with the version Commerce built with - sorry for your inconvenient.
Regards.
/Q
This is great news Quan, I had the same probs in CMS 7.19.2. What i did was to download 7.19.1 separatly, and referenced my workflow project to these DLLs.
Hi Quan,
Should this be fixed with yesterdays release? I am having issues and am not sure if it is the same issue?
Thanks
Adam
Hi,
No, unfortunately the real fix will only come with Commerce 9. Right now the solution is to update Commerce "only" and let it figures out which version suits it best. Don't force an update on Framework or CMS.Core package.
Regards.
/Q
Hey Q,
Thanks for the quick reply. I don't suppose you have a copy of a packages.config for workflows, do you? Also can I upgrade the other projects and just leave the workflow project on a lower version?
Hi,
The workflow project (from the code samples) breaks when updating the episerver framework package. Execute the following steps to reproduce:
Is this a known issue or does anyone has a solution for this?
Regards,
Jeroen