Psake VS Cake

You may use other tools too: psake, make, cake, fake or any other *ake you are familiar with. I look at them as a tools that make build tasks behind simple commands and help me answer: How did I run that code again?

I use the psake PowerShell module to "build" my PowerShell modules. My psakefile.ps1 contains the logic needed to update the manifest with an incremented version, any new function/cmdlet names, and so on. Then it copies everything from .\src\ to .\output\modulename\version. All I do is call Invoke-psake build or Invoke-psake test, and this works great as-is for "pure powershell modules".

I've used psake (powershell+make) https://github.com/psake/psake - the main thing that attracted me to this was that it wasn't an XML based system (Nant/MSbuild), and it handled task prerequisites very nicely. While some devs find powershell a bit of a pain to learn, they generally become useful very quickly, and I think it's useful to be able to do some level of powershelling anyway.

GitHub - psake/psake: A build automation tool written in PowerShell

This is why 90-99% of our builds are done with Cake. It isolates all of it and you can run the build locally if you want.

A good starting point of you want to get started with Cake is our website at https://cakebuild.net/

I don't think it will get too much confusion, but there is a build system called Cake: https://cakebuild.net/

You may use other tools too: psake, make, cake, fake or any other *ake you are familiar with. I look at them as a tools that make build tasks behind simple commands and help me answer: How did I run that code again?

NAnt was quite a popular build tool used by projects of all sizes targeting .NET Framework on Windows. I have written many complex build systems using NAnt in the past. But XML based DSL was quite clunky to use and maintain. Besides, it was always a daunting task to explain to a new dev on the team. With .NET Core/.NET becoming a cross-platform framework, CAKE and FAKE gained a lot of adoption providing a C# and F# based DSL for build tasks accordingly.

Cake (C# Make) - simple, easy to set up, and with a lot of extensions scripting with C#.

I got the example and the answer I needed on this thread: https://github.com/cake-build/cake/discussions/3564

For those not familiar with it, Cake is a build automation system with a C#-based DSL. It is based on the concept of tasks, which are small units of work, like restoring packages, building, or testing, which can have dependencies on, or trigger, other tasks.

Just a note: there's already a very active community of the same name for the build utility Cake.

Looks interesting! Although the name clashes with Cake (C# Make) project which could be confusing - https://cakebuild.net/