You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry for the late response. Short answer: maybe, but I don't think it's worth pursuing.
There are 2 components of Workflow, the runtime and the designer.
3 years ago I run into problems when WF designer were used in mixed project environments (mixed .dll-s targeting standard, core and full framework), see dotnet/sdk#1930 and dotnet/sdk#1522 (comment). As I see, nothing improved on this front.
3 years ago UIPath embraced @dmetzgar's coreWF project (an unofficial port of WF runtime), see UiPath/corewf. They worked hard to make it run on standard and core. As I see, it can load XAML files, but editing them with designer is challenging. It is still in the experimental phase, though I don't know the limitations.
I'm not a professional developer, only an enthusiast, who sees Orleans and Workflow as really powerful technologies, created this Orleans.Activities project as a proof of concept, but I couldn't fight these uphill battles. After @sergeybykov (project lead) left the Orleans project to work on workflows at Temporal (see Why I joined Temporal), I gave up my last hope, that Orleans and Workflow will ever mix. I came back to github now, after 2 years, only to delete all my subscriptions.
My guess is, that Microsoft will never port, or help to port WF runtime and WF designer to anywhere, even though these are used internally and even these are widely used in corporate environments. Nobody knows why.
It's a great project and wish it can alive.
The text was updated successfully, but these errors were encountered: