Ask HN: F/OSS Build Automation for C# | Hacker News Reader

Ask HN: F/OSS Build Automation for C#

4 pointskleevr9 comments

I've been really trying to get comfortable developing in C#.Net, as the platforming at work has been constrained to Microsoft offerings. Presented with a classic blank slate problem, I decided (perhaps in poor judgement and time mis-managed) to invest some time into starting a ('automatable') build process.

Anyways, if you've got a minute and can take a look (link at bottom), recommend any tools/tooling missing, and any good books that speak to these topics. Or, any constructive criticism that occurs to you as it might be entirely to sparse on the details. Thanks!

http://kleevr.blogspot.com/2008/05/c-build-automation-using-svn-havent.html

* I just realized I may have been using 'Ask YC:', when I should've been using 'Ask HN:',... or perhaps 'Ask 1:' *

and just remember shift-8 makes things italic

View on HN

I've implemented systems using CruiseControl.Net and have had pretty decent luck with it.

It works fine with SVN.

Here is a good book to get you started:

http://www.amazon.com/Expert-Delivery-Using-CruiseControl-NE...

Build automation is not a waste of time, it's a sound practice among others. See The Joel Test: 12 Steps to Better Code

http://www.joelonsoftware.com/articles/fog0000000043.html

   1. Do you use source control?
   2. Can you make a build in one step?
   3. Do you make daily builds?
   4. Do you have a bug database?
   5. Do you fix bugs before writing new code?
   6. Do you have an up-to-date schedule?
   7. Do you have a spec?
   8. Do programmers have quiet working conditions?
   9. Do you use the best tools money can buy?
  10. Do you have testers?
  11. Do new candidates write code during their interview?
  12. Do you do hallway usability testing?

I remember reading that article what seems like years ago, and I think's it's always been hanging around in the back of my mind ever since. It was good to read it again-- like re-watching a good movie.

These days I read it an it seems obvious to me, which means Joel did his job well. The "old" Joel is classic.

You have two major choices, NAnt and MSBuild. I recommend you learn MSBuild and how to deal with visual studio with it. That way you'll be more effective in the long run.

Unless, of course, you're not using the MS toolchain. Then NAnt is the only real choice.

Also, you should seriously consider replacing NUnit with mbUnit. It's far more powerful and will save you a lot of time once you get comfortable with it.

First question: are you using source code control? If not, how many developers are on your team? If it's just you and you don't need/want-to use source code control, consider batch file builds scheduled as Scheduled Tasks in XP/Vista/OS.

Yeah, I was thinking I was only a scheduled batch file or two away from some semblance of automation. Also if I could find a XSLT to beautify the XML tree that comes from NUnit.

edit, I'm currently the only developer, but hopefully that won't be true for too long, I've been trying to get our office ready for a collabrative environment, because we're about to step outside the scope of 1-person-1-project

link: http://kleevr.blogspot.com/2008/05/c-build-automation-using-...

Reply on news.ycombinator.com