Aaron Dandy

I also would love a way to handle this. Currently my workaround is to have a task like "set-release" while I default to Debug where the set-release changes a global...

I am working in Visual Studio Online now and with their new secured variable setup I will need to pass some things as parameters. If we can come up with...

Personal taste I guess but `-Pthingy=stuff` is not so easy on the eyes. What about `-parameters "Thing1=one;Thing2=two things"` or `-p Thing1=one -p "Thing2=two things"` . I suppose the first way...

Next question to sort out: A) `scriptcs bau.csx -- -p key=value build` or B) `scriptcs bau.csx -- build -p key=value` Either way I think this will require a large change...

Any work done on this issue will likely clash with changes in PR #203 as it also made changes to argument parsing code.

This would allow tools like Scrawl for example to display a list of tasks that are available to be run from within the IDE.

Do you have any thoughts on how this would work? `scriptcs baufile.csx -- -list` vs `scriptcs baufile.csx -- task-name` ? What if I make a task named `-list` (not that...

I like the description approach much better and it should be easy to implement. Want to include the `.Desc(description)` stuff in this issue as it is pretty much required? `-T`...

Currently Bau allows for whitespace in task names. The easy solution to this problem is to tell people "don't do that" but would it be better to wrap task names...

I wonder if it could cause issues for others when parsing the output. As I think about it though I guess it would be more of an issue if there...