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
Is it possible to get PowerShell to reinterpret the relevant keywords (Workflow, Sequence, InlineScript, Parallel, $WORKFLOW:… scope, etc.) as invocations of the relevant CoreWF names instead of its reliance on Windows Workflow Foundation?
It would be cool if we could modify the PowerShell codebase to allow dependency modularity on Core so that the workflow engine could be swapped out for a library that provides the same functionality.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am used to deploying NuGet packages in PowerShell as imported assemblies, but I wonder if it is possible to use CoreWF as a drop-in replacement for PowerShell Workflow.
Is it possible to get PowerShell to reinterpret the relevant keywords (
Workflow,Sequence,InlineScript,Parallel,$WORKFLOW:…scope, etc.) as invocations of the relevant CoreWF names instead of its reliance on Windows Workflow Foundation?It would be cool if we could modify the PowerShell codebase to allow dependency modularity on Core so that the workflow engine could be swapped out for a library that provides the same functionality.
Related: PowerShell/PowerShell#9570
Beta Was this translation helpful? Give feedback.
All reactions