I've picked up Invoke-Build after considering psake, Cake etc
I like that it supports incremental building which is a key feature of a build orchestration engine. I also like that it isn't a module so it won't pollute my PowerShell runspace or bleed variables back into the caller.
However, I have a minor gripe with the task dependency syntax. Currently I have to define a task and dependencies like so
task Foo Bar, { }
This is very nice and concise, but awkward at the same time. The trailing , to create an array is a bit unfortunate.
Would it be possible at add an optional parameter to specify dependencies like psake has with -depends? I feel this will help other maintainers of my scripts grok them more effectively without the somewhat magical syntax confusing them.
I've picked up Invoke-Build after considering psake, Cake etc
I like that it supports incremental building which is a key feature of a build orchestration engine. I also like that it isn't a module so it won't pollute my PowerShell runspace or bleed variables back into the caller.
However, I have a minor gripe with the task dependency syntax. Currently I have to define a task and dependencies like so
task Foo Bar, { }This is very nice and concise, but awkward at the same time. The trailing
,to create an array is a bit unfortunate.Would it be possible at add an optional parameter to specify dependencies like psake has with
-depends? I feel this will help other maintainers of my scripts grok them more effectively without the somewhat magical syntax confusing them.