SaaSHub helps you find the best software and product alternatives Learn more →
CommandDotNet Alternatives
Similar projects and alternatives to CommandDotNet
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Command Line Parser
The best C# command line parser that brings standardized *nix getopt style, for .NET. Includes F# support
-
-
Fluent Command Line Parser
A simple, strongly typed .NET C# command line parser library using a fluent easy to use interface
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
NFlags
Simple yet powerfull library to made parsing CLI arguments easy. Library also allow to print usage help "out of box".
CommandDotNet discussion
CommandDotNet reviews and mentions
-
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.
-
A note from our sponsor - SaaSHub
www.saashub.com | 13 Jun 2024
Stats
bilal-fazlani/commanddotnet is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of CommandDotNet is C#.
Popular Comparisons
- CommandDotNet VS Sharprompt
- CommandDotNet VS CliFx
- CommandDotNet VS spectre.console
- CommandDotNet VS Sieve
- CommandDotNet VS Fluent Command Line Parser
- CommandDotNet VS Console Framework
- CommandDotNet VS RunInfoBuilder
- CommandDotNet VS Command Line Parser
- CommandDotNet VS SharpNetSH
- CommandDotNet VS NFlags