Adam Ralph

It's a good point about the semantics of silent and quiet. Even though they have the same outcome in v1 and v2 we should respect the semantics. So, I propose:...

IIRC it was one of the CI builds where this problem manifested, probably Travis. Easily reproducible? Probably not :wink:

For reference, this has been implemented for the acceptance testing so one option is to just lift this code out into Bau itself https://github.com/bau-build/bau/blob/13e19b27647881e931dd76884a9500baa7b0d6ed/src/test/Bau.Test.Acceptance/Support/FileSystem.cs

I envisage the `.Directory()` task as just taking a single path which would also serve as the task name, but there could also be a `.Directories("foo").Do(() => directories.Paths(artifactDir, nugetOutputDir, logsDir))`

Can use the outcome of #187

https://github.com/scriptcs/scriptcs/issues/643 was released in scriptcs 0.10

Hi @eatdrinksleepcode, yes, file tasks and dependencies is something I had in mind from early on but I've not got round to doing it yet. I'm not familiar with Gradle...

Yes, I agree, it would be a very natural fit for the Bau API and I definitely want to do this. Initially I think we should release a simple version...

That would be great! What syntax are you thinking of? My guess would be something like: ``` C# Require().File("out.txt").DependsOn("in1.txt", "in2.txt").(file => ...); ``` Where `file` is an instance of something...

I guess the distinction is probably better. In that case, if I had something like: ``` C# bau.Task("foo") .Do(...); bau.Task("bar") .DependsOn("foo) .Inputs("path/to/input1.txt", "path/to/input1.txt") .Outputs("path/to/output1.txt", "path/to/output2.txt") .Do(...); ``` Then a call...