.NET lets you build console applications (or command-line interface (CLI) applications). This section focuses on how to build them and how they are still relevant in this day and age. I’m still baffled by how many CLI’s are used in everyday situations like builds and automated scripts.
There are 3 articles tagged with Console Application.
Console applications are alive and kicking. Setting them up might be a bit hard. In this article I’ll explore how to create a .NET console application that provides commands using the new System.CommandLine package. This will provide arguments to command mapping out of the box. I’ll be showing how to combine it with dependency injection for even more power ⚡.
In ASP.NET Core we are used to have multiple appsettings.json files with settings that differ per environment. I want to do the same in a Console Application. This makes debugging the application easier.
When you are used to building web applications, you kind of get hooked to the ease of Dependency Injection (DI) and the way settings can be specified in a JSON file and accessed through DI (IOptions). It’s only logical to want the same feature is your Console app.
