Build Services (Wonka) Should support a build.bat
AppHarbor and company uses solution files and it looks like you have went with that same architecture. However I think most folks keep their nugets out of their solutions and use some automated build tool to handle that.
Trying to support all of those different automated builds could be a nightmare (it killed horn-get). I say instead, support a build.bat file and require it to build from source without any installation dependencies.
Then have a convention about where the packages should be (or search for the built ones).
Having the build.bat in the root becomes a contract that you will call that file and that the developer can use whatever build tool they want.
Build.bat is all yours (do not we still push *.nupkg as the last step in the build process)
Consider it planned
Thomas Freudenberg commented
Since psake support was rejected in favor of batch files (http://myget.uservoice.com/forums/135675-general/suggestions/3095482-support-psake-based-builds-for-build-services), I'd be fine with a 1-liner invoking powershell.
build.sh is probably a further out pipe dream for now. Supporting build.bat for now would be awesome sauce!
Bash can run them. It might mean cygwin.
Rob, would "build.sh" imply that we have to run Cygwin? Or how would we execute those?
Build.sh as well for folks using not windows
Damian Hickey commented
If I can call my psake default.ps1 from the bat, then I'm cool with this. Building from a solution really doesn't appeal to me.