Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Suggestion: Rake-like task list #56

ryno1234 opened this Issue Feb 8, 2013 · 1 comment


None yet
2 participants

ryno1234 commented Feb 8, 2013

I found psake and got very excited. I think its a very cool tool and answers some of my needs, but I really feel its lacking some items that would make it drastically more viable / easy to use. Take these suggestions with a grain of salt, it could just be my retentiveness. ;)

  • psake and my tasks should be in separate places. They should have no crossover / directory sharing. I realize nothing prevents one from doing this, its simply that the Wiki suggests placing task files there. In my project, I move my 3rd party libraries, tools, etc. to a completely separate folder away from my source code.
  • This could stand to have a better way to initialize the task system when running a task i.e. having this installed to a place like c:\Program Files\Common Files\Modules\psake\ and having that path added to the environment var for powershell's modules (http://msdn.microsoft.com/en-us/library/windows/desktop/dd878350(v=vs.85).aspx). Something as simple as a PowerShell script could do this function. MSI's etc, I dont see are necessary and would be overkill to do this simple task. (Although I do not know if PS is sandboxed from writting in Program Files)
  • It would be great if you could simply type "Invoke-Psake" or something along those lines within a directory, scour the entire tree for tasks based on some mechanism (many options here) and have the result returned to the console listing the tasks available. This would allow you to choose a task and run it, or alternatively use the task names returned to invoke the tasks one by one as needed, again using Invoke-Psake task name.

Again, just my 2 cents. Thank you so much for a great tool!


damianh commented Mar 31, 2014

  1. Psake is distributed via nuget package and is, for most people, in a seperate directory (feel free to make it clearer in the wiki)
  2. Psake can be installed via chocolatey and is made available on your path
  3. While I would like to see something like that, it could be developed externally and contributed later. I don't see the current maintainers building it to be honest.

Am going to close this. If someone does 3), post a seperate issue / PR

@damianh damianh closed this Mar 31, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment