Simple and Effective tool for .NET developers

Introduction to the Make tool for .net developers.
make docs: www.gnu.org/software/make/man...
Support my Work 🤝 / raw_coding
Buy my Courses 📚 learning.raw-coding.dev
Buy my Merch 🛒 shop.raw-coding.dev
Join the Community 💬 / discord
Tweet Tweet 📣 / anton_t0shik
Tune in LIVE! 🎥 / raw_coding
#aspnetcore #dotnet #csharp

[@Xorcist77]

As a primarily .NET/C# development house, we moved away from make scripts early on, jumping over to cake-build which was a C# based scripting tool and it was okay for a while (but was a pain to debug), and then we finally landed on nuke-build, which dynamically builds and runs a full .NET/C# project allowing for maximum customizability. We've used it for all types of build automation, from basic scaffolding to fully testable local CI/CD setups (which in-turn make all our Azure DevOps yaml build files 2-3 lines).

[@RawCoding]

Dude I love nuke, we use make for managing local docker env, database migrations, local env setup etc… not really build & cicd pipeline automation; how do you think nuke will play out for what we’re doing?

[@Qrzychu92]

fun thing is, there is so many flavours of the same concept: psake (powershell make), fake (F# make), cake (C based) and so on. We actually used psake to have local scripts for building all of the stuff - just the app, running tests and converting the results to nice html reports, packing it, building docker images etc. You could run all those scripts locally, while our CICD pipeline would just pass all the needed parameters like build version, prod secrets so on. Worked really well, plus psake has a really nice integration with powershell command line so you can discover actions and their parameters with tab

[@Eldritch_]

That's definitely the best youtube channel to learn c# imo

[@ahjsbkdjhavkcjhvac]

This has been the most useful example to bring ever!!

[@luizfdds]

Nice video! A great and powerful pattern used with Make is the 3 Musketeers.

[@massinemouha6858]

I've been doing this for a while now, even on windows and it's a life saver. GNU tooling is handy and should be appreciated more

[@meetingattender8132]

Nice!! new commands to memorize

[@Mikoshi-solo]

I did a similar approach with PowerShell😂

[@abto6914]

is it just me or my laptop became hotter after the video, holy beard bro

[@cocoscacao6102]

Nice video. I'd recommend scoop over chocolatey.

[@VincentYang024]

Great content and would work perfectly if your tooling requirement is simple like this. I tried it after watching your video, when it works, it's like a charm, It has a lot of pain as soon as you start using it with a bit complex build. I'm pulling my hair to fix a few basic issues between Windows and other OS that caused script failure. At this stage, I will invest a bit more on "Nuke"

[@djoufson-dev]

Awesome video, but is there any advantage of using 'make' tool instead of regular script files? I used to register my most used commands in a .sh file inside a scripts folder in a way I can reuse those by running the script 🤔

[@gustavo-santos-dev]

This is funny because I'm mainly a .NET SWE, but I also code in Go, where using Makefiles is a common practice, but I never thought of using it in .NET projects. 😂

[@mt89vein]

You can do it via rider built in tool in context menu

[@sunnypatel1045]

Ohh interesting

[@ivandrofly]

what is your pc specs?

[@haribalachander]

Do you face issues with .Net programming in a Mac ?

[@RawCoding]

Nope

[@alirezanet]

hey Anton, why do you look like me bro !! 😂😁

[@MultiSteve1978]

I wrote a lot of c -> c# wrappers. To describe the dependencies and regenerate the c# projects i use the good old make tool. May it’s possible to run migration automatically if the migration files are older than any of the source files in the database project. But be careful if you use git 😂

[@soonhongng7037]

how is this a big difference to bashscript

[@RawCoding]

Its not that big of a difference, you can treat makefile as the interface and bashscrips are internals that you call out to; or just use bash files directly

[@7th_CAV_Trooper]

I think migrations suck. I hate them. Makes me want to avoid EF. Is it just me, or is this the worst part of using RDBMS systems with dotnet?

[@gustavo-santos-dev]

Migrations is an optional feature, just use it when you want to use 100% code-first approach. You can use EF without migrations, just create the mapping to your tables and don't add the code to execute the migrations, it's great and it's what I use in most of my projects.

[@7th_CAV_Trooper]

@@gustavo-santos-dev fair enough. I keep encountering 3rd party software that requires them though. Like Identity Server. Seems like these could just be nuget packages.

Yeah, I don't like it either. I use EF without migrations because I prefer the DB First approach.