simple-exec
UpdatR
Our great sponsors
simple-exec | UpdatR | |
---|---|---|
3 | 2 | |
643 | 5 | |
- | - | |
8.1 | 6.4 | |
16 days ago | 11 days ago | |
C# | C# | |
Apache License 2.0 | MIT License |
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
UpdatR
-
What is the/your current/popular choice for dotnet c# scripting ?
With top level statements a .cs-file can be quite similar to csx. I just whish I could specify the nuget packages in it so we could ditch the csproj. Or that csx for full support in dotnet run. I usually just use top level statements with Bullseye, that's quite neat even if it requires a csproj. Here's an example of what I do with it: https://github.com/OskarKlintrot/UpdatR/blob/main/tools/Build/Build.cs
-
I've been wasting time writing Clone libraries. What's your free time project?
My side project is UpdatR (https://github.com/OskarKlintrot/UpdatR) which I use to replace Nukeeper at work. Nukeeper is deprecated and stopped working on Azure DevOps but Dependabot isn't available on Azure DevOps. "How hard can it be" I thought and spent too many evenings getting it working good enough to actually use... It updates packages to the latest version that is still supported by the target framework and generates a title and body to be used in the PR. It seems to be working so far. I want it to support multitarget frameworks and updating Directory.Build.props too, which are no small tasks...
What are some alternatives?
ScriptCS - Write C# apps with a text editor, nuget and the power of Roslyn!
csharpier - CSharpier is an opinionated code formatter for c#.
NuKeeper - Automagically update nuget packages in .NET projects
ClearScript - A library for adding scripting to .NET applications. Supports V8 (Windows, Linux, macOS) and JScript/VBScript (Windows).
FAKE - FAKE - F# Make
dotnet-script - Run C# scripts from the .NET CLI.
Cake - :cake: Cake (C# Make) is a cross platform build automation system.
bullseye - 🎯 A .NET library for running a target dependency graph.
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.
Marten - .NET Transactional Document DB and Event Store on PostgreSQL