PowerShell Workflows: Nesting

re: PowerShell Workflows: Nesting

Richard Siddaway — Tue, 15 Jan 2013 13:31:29 GMT

Thank you for the feedback. Glad the articles are proving useful.

Yes in theory you can convert a PowerShell module (I'm assuming you mean a script module) into workflows. the question rather should you do it? Workflows are one possible solution to a problem but they might not be the best. I wouldn't automatically rush to converting everything to workflows. If you need the things that workflows bring such as mixing parallel & sequential processing or the ability to restart tasks then workflows are probably your answer.

I'm a big believer in keeping things simple and workflows are complicated. The 7th article in the series will cover when to use workflows and when to use other mechanisms such as PowerShell jobs in greater detail

re: PowerShell Workflows: Nesting

Jeffrey S. Patton — Wed, 09 Jan 2013 22:32:35 GMT

Love this, so it sounds like you could turn existing psm1 function modules psm1 workflow modules! Or even combine elements of both? Is there a way to make sure that if your workflow module is imported into a non powershell 3 host it won't crash? I've not actually tested to see if that happens...but it would seem to be if posh2 doesn't know what a workflow is, then it may will prevent the module from loading.

Great article!

re: PowerShell Workflows: Nesting

K_Schulte — Wed, 09 Jan 2013 09:42:37 GMT

Hi Richard,

This is again ... another GREAT blog post targeting a very iinteresting topic: PS workflows!

I can't wait to read your next post on how to control worklfows!!

Thank you very much!!!

Klaus.