UnionArgParser
CliWrap
Our great sponsors
| UnionArgParser | CliWrap | |
|---|---|---|
| 3 | 15 | |
| 436 | 4,126 | |
| 1.8% | - | |
| 7.8 | 8.0 | |
| 15 days ago | 5 days ago | |
| F# | 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.
UnionArgParser
-
From Script to Scaffold in F#
More formal argument parsing using the Argu library
-
Anyone interested in doing some 1 on 1 consulting?
Create a user interface (can start as Console.Readline() or Argu, or you can just go all in and write something with avalonia/fable)
-
Really great example projects?
Personally, I like how the Argu library is written: https://github.com/fsprojects/Argu
CliWrap
-
ModularPipelines - Strong-Typed, Parallel, C# Pipelines - Would appreciate feedback and thoughts
That being said, keep up the good work. I see a lot of potential in combo with libs like https://github.com/Tyrrrz/CliWrap
-
Process Ids on C#
Check out CliWrap. https://github.com/Tyrrrz/CliWrap
-
A History of the FFmpeg Project
I am using CliWrap to create my own wrapper for the functionality I need from FFmpeg. Works pretty well!
https://github.com/Tyrrrz/CliWrap
-
Creating a service that runs other executables (Windows Server)
Take a look at https://github.com/Tyrrrz/CliWrap for calling another process from one process.
- Calling PowerShell Azure module and creating resource group from C#
-
Why do Task.Wait and Task.Result even exist?
For example, using the great Cli.Wrap library:
-
Add persisted parameters to CLI applications in .NET
We can use Verify to perform snapshot testing and check for the correct output of the program. In order to make things easier and simplify working with process output capturing and invocation, I used CliWrap.
- GUI for a command line program
-
I Want Off Mr. Golang's Wild Ride
> You can take a look at System.Diagnostics.Process for one of the worst offenders.
Yeah, this is one of my least favourite APIs in all of .NET. My understanding is that the .NET team is planning to redo it in the next few years, but if you want something better right now I highly recommend the excellent CliWrap library: https://github.com/Tyrrrz/CliWrap
-
A 3 minute video on how to use PowerShell directly in C#
I religiously use CliWrap which makes things a bit easier, but still issues on some things like Async Processes and the start thing i spoke about
What are some alternatives?
EntryPoint - Composable CLI Argument Parser for all modern .Net platforms.
Sieve - ⚗️ Clean & extensible Sorting, Filtering, and Pagination for ASP.NET Core
ReadLine - A Pure C# GNU-Readline like library for .NET/.NET Core
Command Line Parser - The best C# command line parser that brings standardized *nix getopt style, for .NET. Includes F# support
clipr - Command Line Interface ParseR for .Net
Fluent Command Line Parser - A simple, strongly typed .NET C# command line parser library using a fluent easy to use interface
Power Args - The ultimate .NET Standard command line argument parser
spectre.console - A .NET library that makes it easier to create beautiful console applications.
Docopt - Port of docopt to .net
CsConsoleFormat - .NET C# library for advanced formatting of console output [Apache]
Appccelerate - Command Line Parser - A simple command line parser with fluent definition API.
SharpNetSH - A simple netsh library for C#