The current implementation only supports one NuGet operation per BauTask. The fluent interface as well as the Task implementations should be rearrange to support this.
My current thoughts are that after #5 is complete a NuGetBauTaskBase would just store a collection of requests that would all be executed in the BauTask OnActionsExecuted()
The For() method (likely an extension method) would need to accept IEnumerable<string> as well as params string[]. For each target file a request would be created, queued with the task and then returned for use with fluent operations.
The current implementation only supports one NuGet operation per
BauTask
. The fluent interface as well as the Task implementations should be rearrange to support this.My current thoughts are that after #5 is complete a
NuGetBauTaskBase
would just store a collection of requests that would all be executed in the BauTaskOnActionsExecuted()
The
For()
method (likely an extension method) would need to acceptIEnumerable<string>
as well asparams string[]
. For each target file a request would be created, queued with the task and then returned for use with fluent operations.