How do I create multiple commands like git push and pull in PowerArgs?

Use the [ArgActionMethod] attribute on methods in your class. PowerArgs will automatically invoke the correct method based on the first argument, as demonstrated in the calculator program with separate add, subtract, multiply, and divide actions.

PowerArgs vs System.CommandLine – which is better for .NET?

PowerArgs excels for complex, action-based CLI tools with built-in validation and tab completion, while System.CommandLine might be lighter for simpler parsing needs. Choose based on whether you need advanced features like customizable help templates.

How to add custom validation rules in PowerArgs?

Create a class that derives from ArgValidator and apply it as an attribute to properties. The README shows an example with [UsPhoneNumber], and you can implement similar validators for specific business logic.

Can PowerArgs generate HTML help documentation?

Yes, it includes a browser-friendly usage template that outputs HTML. You can use ArgUsage.GenerateUsageFromTemplate() with the built-in web template or create custom ones, as linked in the README example.

How to handle secure inputs like passwords with PowerArgs?

Use the SecureStringArgument type for properties. It prompts users without displaying input, and you can access the value via the SecureString property or ConvertToNonsecureString method, ensuring sensitive data isn't visible on the command line.

Open-Awesome

Power Args

MITHTML

A .NET Standard command line argument parser that converts arguments into .NET objects with validation, auto-generated usage, and tab completion.

GitHub

577 stars57 forks0 contributors

What is Power Args?

PowerArgs is a .NET Standard library for parsing command line arguments into strongly-typed .NET objects. It automates argument validation, generates usage documentation, and orchestrates program execution based on actions, reducing boilerplate code for CLI applications. It solves the problem of manual argument parsing and error handling in .NET command line tools.

Target Audience

.NET developers building command line applications, tools, or utilities that require robust argument parsing, validation, and user-friendly help systems.

Value Proposition

Developers choose PowerArgs for its comprehensive feature set—including validation, tab completion, and auto-generated documentation—coupled with a clean, attribute-based API that minimizes boilerplate. Its ability to handle complex scenarios like multi-action programs and secure input makes it a versatile alternative to basic parsing solutions.

Overview

The ultimate .NET Standard command line argument parser

Use Cases

Best For

Building .NET command line tools with multiple actions (e.g., git-style interfaces)
Adding robust argument validation and user-friendly error messages to CLI applications
Generating customizable help documentation from templates for console or web
Implementing tab completion for command line argument names
Parsing secure inputs like passwords without displaying them on the command line
Creating extensible CLI frameworks with custom type converters and validators

Not Ideal For

Projects requiring only basic, no-frills argument parsing without validation or actions
Cross-platform applications not built on the .NET framework
Environments where minimizing third-party dependencies is a top priority
Teams preferring fluent, code-first APIs over attribute-based configuration

Pros & Cons

Pros

Action-Based Execution

Automatically routes and invokes methods based on command line actions, enabling git-style multi-command interfaces as shown in the calculator example.

Comprehensive Validation

Includes built-in validators for required fields, ranges, regex, and file existence, reducing manual error-checking boilerplate.

Customizable Help Templates

Generates usage documentation from templates that can be tailored for console or web output, offering flexibility in presentation.

Tab Completion Support

Enables tab completion for argument names and allows custom completion sources, enhancing CLI usability.

Cons

Attribute-Heavy Syntax

Requires extensive property decoration with attributes, which can clutter class definitions and increase verbosity compared to fluent APIs.

Complex Extensibility Setup

Implementing custom revivers or tab completion sources involves additional classes and interfaces, adding to the initial learning curve.

.NET-Only Limitation

Tied exclusively to the .NET ecosystem, making it unsuitable for projects using other languages or frameworks.

Frequently Asked Questions

Related Projects

spectre.console

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

Stars11,534

Forks666

Last commit2 days ago

Gui.cs

Cross Platform Terminal UI toolkit for .NET

Stars11,092

Forks779

Last commit17 hours ago

Command Line Parser

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

Stars4,819

Forks477

Last commit2 years ago

CommandLineUtils

Command line parsing and utilities for .NET

Stars2,273

Forks261

Last commit10 hours ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub