this post was submitted on 19 Nov 2024
7 points (100.0% liked)
.NET
1482 readers
12 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
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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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
Makes sense. So far I've been able to do all that within the project file itself with tasks and property files.