CommandDotNet
Command Line Parser
Our great sponsors
CommandDotNet | Command Line Parser | |
---|---|---|
3 | 17 | |
550 | 4,397 | |
- | 1.7% | |
5.9 | 0.0 | |
3 months ago | about 2 months ago | |
C# | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
CommandDotNet
-
Simple Command line Project Helper (Would love feedback)
Have you seen https://github.com/bilal-fazlani/commanddotnet? Disclaimer: I'm one of the maintainers What you've thrown together does seem similar to CliFx in some respects, as you mentioned in another thread. It looks like a command must be defined as a class. I once created a framework that followed that approach and ultimately found it limiting. I've found it to be more expressive to use methods to define commands, although both are possible with CommandDotNet. For example, we can use the position of parameters in the methods to define the position in the command. Defining operands (positional parameters) via properties, we automatically position them based on position in the file, which was interesting because .net does not guarantee order of properties when reflecting them. We were able to use CallerLineNumber to get this. You might look into that. To answer the question of `Is the use of the project simple and have any benefit over using other parsers?` I'd say that CommandDotNet, CliFx, Spectre and even MS's System.CommandLine have a head start on tackling some of the more complex features and already have some community around them. It think this project has a bit of catchup to do. For example, you can see the CommandDotNet features at https://commanddotnet.bilal-fazlani.com/features/ A lot of the design went into making it a simple as possible to define a command using c# conventions, like parameter positions, NRT, optional parameters, etc. Fore example, we use nullability to determine if an argument is required, although it's also possible to use DataAnnotations or FluentValidations to perform more complex validations. That all takes a bit of time to support. I'd say if you're looking to experiment and play around, keep at it. It's unlikely you're going to get a lot traction in the space though, especially since MS has their own framework. If you want to contribute code that's more likely to be used and seen by others, look at System.CommandLine or one of the other main tools. If you continue with this one, feel free to use CommandDotNet for reference if you'd like hit me up for questions on the discussions, or feel free to bring ideas to CommandDotNet and contribute.
-
How to generate a CLI interface for CRUD operations?
Someone asked a similar question about a https://github.com/bilal-fazlani/commanddotnet/, which is a tool I help maintain.
-
Spectre.Console is a .NET Standard 2.0 library that makes it easier to create beautiful console applications.
Have you seen CommandDotNet by chance? It has an integration with Spectre.Console. It provides some powerful test tools and what I think is a simpler and more flexible way to define commands.You can check out the features page to see what's available.
Command Line Parser
-
Parse CLI arguments in .NET
So after some research I found the awesome NuGet-Package Command Line Parser Library. This package allows to define your options with Property-Attributes.
- Is it possible to pass variables from PHP to a C# console app?
- How to generate a CLI interface for CRUD operations?
-
Made this a while ago and forgot to share it here -- ArgSharp, a simple and capable CLI argument parser
seems very similar to command line parser, btw good job
-
having trouble understanding the new "method chaining" syntax
The URL of the library is at https://github.com/commandlineparser/commandline. This project page has samples for VB.Net, along with other languages too.
-
IS there any way to change string[] args to an object on the fly?
How about https://github.com/commandlineparser/commandline ?
-
Developing and installing your own CLI with dotnet tool and CliFx NuGet package
This lib looks way better than the seemingly most popular one: https://github.com/commandlineparser/commandline Which is just a nightmare with terrible docs
- What's your favorite command line arg parser?
- What is your preferred way to roll for stats?
-
Reverse Engineering Keyboard Driver: Part 2 (Decompiling .NET applications)
CommandLineParser
What are some alternatives?
Sharprompt - Interactive command-line based application framework for C#
Fluent Command Line Parser - A simple, strongly typed .NET C# command line parser library using a fluent easy to use interface
CliFx - Class-first framework for building command-line interfaces
spectre.console - A .NET library that makes it easier to create beautiful console applications.
CommandLineUtils - Command line parsing and utilities for .NET
Sieve - ⚗️ Clean & extensible Sorting, Filtering, and Pagination for ASP.NET Core
Power Args - The ultimate .NET Standard command line argument parser
Cocona - Micro-framework for .NET console application. Cocona makes it easy and fast to build console applications on .NET.
Console Framework - Cross-platform toolkit for easy development of TUI applications.
CliWrap - Library for running command-line processes