Cocona VS CommandDotNet

Compare Cocona vs CommandDotNet and see what are their differences.

Cocona

Micro-framework for .NET console application. Cocona makes it easy and fast to build console applications on .NET. (by mayuki)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
Cocona CommandDotNet
7 3
2,966 549
- -
5.8 5.9
24 days ago 2 months ago
C# C#
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

Cocona

Posts with mentions or reviews of Cocona. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-11-11.

CommandDotNet

Posts with mentions or reviews of CommandDotNet. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-12-17.
  • Simple Command line Project Helper (Would love feedback)
    3 projects | /r/csharp | 17 Dec 2022
    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?
    2 projects | /r/dotnet | 11 Dec 2022
    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.
    3 projects | /r/dotnet | 23 Sep 2022
    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.

What are some alternatives?

When comparing Cocona and CommandDotNet you can also consider the following projects:

Sharprompt - Interactive command-line based application framework for C#

Command Line Parser - The best C# command line parser that brings standardized *nix getopt style, for .NET. Includes F# support

spectre.console - A .NET library that makes it easier to create beautiful console applications.

CliFx - Class-first framework for building command-line interfaces

command-line-api - Command line parsing, invocation, and rendering of terminal output.

CSharpRepl - A command line C# REPL with syntax highlighting – explore the language, libraries and nuget packages interactively.

Sieve - ⚗️ Clean & extensible Sorting, Filtering, and Pagination for ASP.NET Core

Fluent Command Line Parser - A simple, strongly typed .NET C# command line parser library using a fluent easy to use interface

Console Framework - Cross-platform toolkit for easy development of TUI applications.

RunInfoBuilder - A unique command line parser for .NET that utilizes object trees for commands.