submitted 5 months ago by BlueSerendipity8@programming.dev to c/dotnet@programming.dev

4 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] BlueSerendipity8@programming.dev 4 points 5 months ago

Cake is an imperative and task-based way of expressing builds. In my opinion, it truly provides its benefits when you have a complex build pipeline. The added value is that any C# developer can understand and contribute to the build process without needing to master bash or PowerShell scripting languages or figure out how to use declarative DSLs like GitHub Actions, AppVeyor, or GitLab CI

[-] GetOffMyLan@programming.dev 1 points 5 months ago* (last edited 5 months ago)

Makes sense. So far I've been able to do all that within the project file itself with tasks and property files.

[-] Kissaki@programming.dev 1 points 5 months ago* (last edited 5 months ago)

I'm surprised you didn't mention MSBuild. dotnet runs MSBuild, and MSBuild is task-oriented (or target-oriented? or target-task-oriented?).

I take editing via MSBuild would cover the same things, but Cake allows doing so without having to use/learn MSBuild?

this post was submitted on 19 Nov 2024

7 points (100.0% liked)

.NET

1653 readers

16 users here now

Getting started

Useful resources

IDEs and code editors

Visual Studio (Windows/Mac)
Rider (Windows/Mac/Linux)
Visual Studio Code (Windows/Mac/Linux)

Tools

Decompilers: ILSpy, dotPeek
Scratchpad: LINQPad
Online playground and IL viewer: SharpLab

Rules

Rule 1: Follow Lemmy rules
Rule 2: Be excellent to each other, no hostility towards users for any reason
Rule 3: No spam of tools/companies/advertisements

Related communities

Wikipedia pages

.NET (open source & cross platform)
.NET Framework (proprietary & Windows-only)

founded 2 years ago

MODERATORS

erlingur@programming.dev

starman@programming.dev

Spyros@programming.dev