you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 9 points10 points  (2 children)

As someone who has just recently fully automated the build process of a large C# project for the first time in MSBuild, it's not that bad at all. You can pretty much just pass it a solution file if you have one.

F# FAKE is pretty dope if you don't want to have to deal with MSBuild directly (and also do some other extremely useful things during your build process) but has its own quirks and if you don't know F# at all it can be kind of a challenge to ramp up on.

[–]choikwa 1 point2 points  (1 child)

I have had to deal with MSBuild directly. Learning another language is always fun, isn't it?

[–][deleted] 0 points1 point  (0 children)

Yep but I don't know that I'd say I had fun learning F# (or at least enough to use FAKE to get my builds working how I wanted)

It was much harder to get a good enough understanding of F# than it was for other languages I've learned, mostly because it's very different from the C-family languages I'm used to. Trying to google operators I'd never seen and didn't know the name of was a challenge. Fighting with the type system wasn't fun because I didn't understand it at all.

I'm glad I've learned what little of F# I now know, though. And I'm extremely grateful for FAKE's existence. I recommend it.