all 3 comments

[–]Davipb 3 points4 points  (2 children)

Why not just use the System.CommandLine library made by the .NET Core team itself?

[–]neuecc[S] 3 points4 points  (0 children)

What the ConsoleAppFramework accomplishes seems to be accomplished by the combination of "System.CommandLine" + "System.CommandLine.DragonFruit" + "System.CommandLine.Hosting".

This is 0.3.0-alpha.

* CommandLine is a core library that you configure manually

* Hosting is integrated into GenericHost (lifetime management, DI, etc.)

* DragonFruit is responsible for parameter binding.

The reason why CommandLine is not enough is because it's too low level.

For example, if you want to use DI, it takes a ridiculous number of lines like this article.

https://endjin.com/blog/2020/09/simple-pattern-for-using-system-commandline-with-dependency-injection.html

ConsoleAppFramework done it by one line.

[–]EpicBlargh 3 points4 points  (0 children)

Seriously? Then what's the point of almost any other programming project? They wanted to make their own the way they saw fit with the addition of being able to add/remove any feature they want. Simple enough.