Aiursoft.CommandFramework 7.0.5
Aiursoft CommandFramework
Aiursoft CommandFramework is a framework for building command line tools.
- Auto argument parsing
- Auto help page generation
- Auto version page generation
With this framework, you can build a command line tool with just a few lines of code.
Example project it built:
C:\workspace> ninja.exe
Description:
Nuget Ninja, a tool for detecting dependencies of .NET projects.
Usage:
Microsoft.NugetNinja [command] [options]
Options:
-p, --path <path> (REQUIRED) Path of the projects to be changed.
--nuget-server <nuget-server> If you want to use a customized nuget server instead of the official nuget.org,
--token <token> The PAT token which has privilege to access the nuget server.
-d, --dry-run Preview changes without actually making them
-v, --verbose Show detailed log
-?, -h, --help Show help and usage information
Commands:
all, all-officials The command to run all officially supported features.
remove-deprecated The command to replace all deprecated packages to new packages.
upgrade-pkg The command to upgrade all package references to possible latest and avoid conflicts.
clean-pkg The command to clean up possible useless package references.
clean-prj The command to clean up possible useless project references.
Why this project?
Command-line applications are a great way to automate repetitive tasks or even to be your own productivity tool. But building a command-line application in .NET is not easy. You need to parse the arguments, generate help pages, and so on. This project is designed to help you build a command-line application with just a few lines of code.
Installation
Run the following command to install Aiursoft.CommandFramework
to your project from nuget.org:
dotnet add package Aiursoft.CommandFramework
First, write a simple class to provide options to your command:
using System.CommandLine;
using Aiursoft.CommandFramework.Models;
public static class OptionsProvider
{
public static RootCommand AddGlobalOptions(this RootCommand command)
{
var options = new Option[]
{
CommonOptionsProvider.DryRunOption,
CommonOptionsProvider.VerboseOption
};
foreach (var option in options)
{
command.AddGlobalOption(option);
}
return command;
}
}
In your YourProject.ExecutableCli
, write the program entry like this:
// Program.cs
using Anduin.Parser.Core.Framework;
using Aiursoft.CommandFramework;
using Aiursoft.CommandFramework.Extensions;
return await new AiursoftCommand()
.Configure(command =>
{
command
.AddGlobalOptions()
.AddPlugins(new CalendarPlugin());
})
.RunAsync(args);
Yes, I know you need to write plugins for your executable!
Now try to write a plugin:
using System.CommandLine;
using Aiursoft.CommandFramework.Abstracts;
using Aiursoft.CommandFramework.Framework;
using Aiursoft.CommandFramework.Models;
using Aiursoft.CommandFramework.Services;
using Microsoft.Extensions.DependencyInjection;
public class CalendarPlugin : IPlugin
{
public CommandHandler[] Install()
{
return new CommandHandler[]
{
new CalendarHandler(),
};
}
}
public class CalendarHandler : CommandHandler
{
public override string Name => "calendar";
public override string Description => "Show calendar.";
public override void OnCommandBuilt(Command command)
{
command.SetHandler(
Execute, CommonOptionsProvider.VerboseOption);
}
private async Task Execute(bool verbose)
{
var host = ServiceBuilder
.BuildHost<Startup>(verbose)
.Build();
await host.StartAsync();
var calendar = host.Services.GetRequiredService<CalendarRenderer>();
calendar.Render();
}
}
public class Startup : IStartUp
{
public void ConfigureServices(IServiceCollection services)
{
services.AddScoped<CalendarRenderer>();
}
}
public class CalendarRenderer
{
public void Render()
{
Console.WriteLine("Hello world!");
}
}
That's it!
$ yourapp calendar
Hello world!
Advanced Usage - Nested Command Handler
Of course, handlers can be nested:
public class GetHandler : CommandHandler
{
public override string Name => "get";
public override string Description => "Get something.";
public override CommandHandler[] GetSubCommandHandlers()
{
return new CommandHandler[]
{
new DataHandler(),
new HistoryHandler(),
new CalendarHandler()
};
}
}
When your app starts, it just works!
$ yourapp get calendar
Hello world!
Advanced Usage - More options
Of course, you can add more options to a specific command:
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Hosting;
using System.CommandLine;
using Aiursoft.CommandFramework.Framework;
using Aiursoft.CommandFramework.Services;
public class TranslateHandler : CommandHandler
{
private readonly Option<string> _bingApiKey = new(
aliases: new[] { "--key", "-k" },
description: "The Bing API Key.")
{
IsRequired = true
};
private readonly Option<string> _targetLang = new(
aliases: new[] { "--language", "-l" },
description: "The target language code. For example: zh, en, ja")
{
IsRequired = true
};
public override string Name => "translate";
public override string Description => "The command to start translation based on Bing Translate.";
public override Option[] GetCommandOptions()
{
return new Option[]
{
_bingApiKey,
_targetLang
};
}
public override void OnCommandBuilt(Command command)
{
command.SetHandler(
Execute,
OptionsProvider.PathOptions,
OptionsProvider.DryRunOption,
OptionsProvider.VerboseOption,
_bingApiKey,
_targetLang);
}
private Task Execute(string path, bool dryRun, bool verbose, string key, string targetLang)
{
var hostBuilder = ServiceBuilder.BuildHost<StartUp>(verbose);
hostBuilder.ConfigureServices(services =>
{
services.AddSingleton(new TranslateOptions
{
APIKey = key,
TargetLanguage = targetLang
});
});
var entry = hostBuilder
.Build()
.Services
.GetRequiredService<TranslateEntry>();
return entry.OnServiceStartedAsync(path, !dryRun);
}
}
Now you have more options to use:
$ yourapp translate --key AB123 --language zh-CN
If you want to explorer a real project built with this framework, please check Parser as an example.
How to contribute
There are many ways to contribute to the project: logging bugs, submitting pull requests, reporting issues, and creating suggestions.
Even if you with push rights on the repository, you should create a personal fork and create feature branches there when you need them. This keeps the main repository clean and your workflow cruft out of sight.
We're also interested in your feedback on the future of this project. You can submit a suggestion or feature request through the issue tracker. To make this process more effective, we're asking that these include more information to help define them more clearly.
Showing the top 20 packages that depend on Aiursoft.CommandFramework.
Packages | Downloads |
---|---|
Aiursoft.Dotlang.Core
Package Description
|
7 |
Anduin.HappyRecorder.PluginFramework
Package Description
|
4 |
Aiursoft.NiBot.Dedup
Nuget package of 'Dedup' provided by Aiursoft
|
0 |
.NET 7.0
- Microsoft.Extensions.Hosting (>= 7.0.1)
- System.CommandLine (>= 2.0.0-beta4.22272.1)
Version | Downloads | Last updated |
---|---|---|
8.0.6 | 90 | 10/09/2024 |
8.0.5 | 10 | 10/07/2024 |
8.0.4 | 165 | 07/09/2024 |
8.0.3 | 40 | 06/28/2024 |
8.0.2 | 12 | 06/27/2024 |
8.0.1 | 194 | 03/25/2024 |
8.0.0 | 3 | 03/26/2024 |
7.0.25 | 6 | 04/26/2024 |
7.0.24 | 5 | 04/26/2024 |
7.0.23 | 5 | 04/06/2024 |
7.0.22 | 3 | 04/26/2024 |
7.0.21 | 4 | 04/26/2024 |
7.0.20 | 4 | 04/26/2024 |
7.0.19 | 4 | 04/26/2024 |
7.0.18 | 4 | 04/26/2024 |
7.0.17 | 4 | 04/26/2024 |
7.0.16 | 7 | 04/26/2024 |
7.0.15 | 3 | 04/26/2024 |
7.0.14 | 4 | 04/26/2024 |
7.0.13 | 3 | 04/26/2024 |
7.0.12 | 4 | 04/26/2024 |
7.0.11 | 6 | 04/26/2024 |
7.0.10 | 5 | 04/26/2024 |
7.0.9 | 5 | 04/26/2024 |
7.0.8 | 4 | 04/26/2024 |
7.0.7 | 3 | 04/26/2024 |
7.0.6 | 3 | 04/26/2024 |
7.0.5 | 4 | 04/26/2024 |
7.0.4 | 6 | 04/26/2024 |
7.0.3 | 4 | 04/19/2024 |
7.0.2 | 4 | 04/26/2024 |
7.0.1 | 3 | 04/26/2024 |
7.0.0 | 6 | 04/26/2024 |
6.0.0 | 4 | 04/26/2024 |
1.0.0 | 4 | 04/26/2024 |