simple-exec
FAKE
Our great sponsors
simple-exec | FAKE | |
---|---|---|
3 | 4 | |
653 | 1,277 | |
- | 0.6% | |
8.1 | 5.8 | |
7 days ago | 2 months ago | |
C# | F# | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
simple-exec
-
What is the/your current/popular choice for dotnet c# scripting ?
I personally use Bullseye and SimpleExec instead of Nuke. I really like sticking to "normal" C#. I used Cake before but never liked it.
-
.NET build tool using Bullseye and SimpleExec
I personally advocate Bullseye in combination with SimpleExec as a build tool for .NET projects due to its sheer simplicity by providing a bare bones API to define the tasks and their dependent tasks in plain C# code. Both these libraries are build by Adam Ralph. It does not enforce any specific model or structure to write your build tasks. When someone runs through the build script, it is fairly straight forward to understand whats going on. We use this build tool setup for Marten for both local dev and CI build tasks and has worked well so far. Also many OSS projects have adopted it.
-
Are there any reasons for .NET developers learning Powershell ?
add simple-exec and you’ve unlocked bash scripts as well
FAKE
-
Achieving single command Infrastructure deployment using PowerShell DSC.
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?
-
.NET build tool using Bullseye and SimpleExec
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.
-
Scala at Scale at Databricks
Check out https://fsprojects.github.io/Paket/ and https://fake.build/ and https://docs.microsoft.com/en-us/dotnet/fsharp/get-started/get-started-vscode for playing with F#.
-
What build tool(s) do people use for their applications?
Cake and Fake are both quite popular in the OSS world.
What are some alternatives?
ScriptCS - Write C# apps with a text editor, nuget and the power of Roslyn!
Cake - :cake: Cake (C# Make) is a cross platform build automation system.
ClearScript - A library for adding scripting to .NET applications. Supports V8 (Windows, Linux, macOS) and JScript/VBScript (Windows).
NUKE - 🏗 The AKEless Build System for C#/.NET
dotnet-script - Run C# scripts from the .NET CLI.
MSBuild - The Microsoft Build Engine (MSBuild) is the build platform for .NET and Visual Studio.
UpdatR - Update tool for package reference and dotnet-tools.json
Psake - A build automation tool written in PowerShell
Invoke-Build - Build Automation in PowerShell
interactive - .NET Interactive combines the power of .NET with many other languages to create notebooks, REPLs, and embedded coding experiences. Share code, explore data, write, and learn across your apps in ways you couldn't before.
Nake - Magic script-based C# task runner for .NET Core