>Speaking from a point of view of complete ignorance, what do the powershell scripts give you that ctrl+shift+b in visual studio doesn't?
The ability to build without having to open visual studio ;)
To build with psake, right click on invokebuild.ps1 in explorer -> run with powershell... and that's it.
Ayende has an interesting
post on psake. It doesn't replace msbuild, doesn't require isn't anything extra to install and doesn't stop a user opening in VS and ctrl+shift+b. Only point of friction is to perhaps enable running of unsigned scripts, which most devs seem to do
So with a right-click + run, I am intending the following steps, for my team anyway:
- (Possibly) update the assembly file version with CI build version
- Run all unit tests / specs
- Create a NuGet pack
- Copy the build output to a build dir ('build') with just the artifacts a user may need.
I have my StoryQ fork being built on my company's CI (TeamCity) and the above helps a lot. In my own projects (none oss yet) I also run reports such as code coverage and style cop. But that is out of scope here :)
I personally love when an OSS project comes with a single .bat or similar to just does the build and puts it all together.
Have you considered making StoryQ builds available via http://teamcity.codebetter.com (login as guest)? It could be useful for people to easily get new builds from your repo without waiting for a release.
In any case, it's up to yourself, it won't affect my contributions. If you decide not to take it, do something else (or nothing at!), I'll move it off to my own separate branch (or something similar) for my own purposes.
And you are welcome :)