Calabonga.Commandex.Shell.Develop.Template
5.0.1
dotnet new install Calabonga.Commandex.Shell.Develop.Template@5.0.1
Calabonga.Commandex.Shell.Develop
Description
This is a nuget-package Calabonga.Commandex.Shell.Develop.Template (tools) that install to your Visual Studio a new type of the project. New type project can create a Developer version of the Command Executer (Calabonga.Commandex). Witch is created to runs commands of any type for any purposes. For example, to execute a stored procedure or just to copy some files to some destination. And so on...
What is Calabonga.Commandex
The Calabonga.Commandex - This is an application on WPF-platform built with CommunityToolkit.MVVM for modules (plugins) using: launch and execute.
What is the Calabonga.Commandex can:
- Find a modules
.dll(plugins) in the folder you set up. - Launch or execute modules
.dll(plughis) from GUI. - Get the results of the module's (plugis) work after they completed.
It's a complex solution with a few repositories:
- Calabonga.Commandex.Shell → Command Executer or Command Launcher. To run commands of any type for any purpose. For example, to execute a stored procedure or just to copy some files to some destination.
- Calabonga.Commandex.Commands → Commands for Calabonga.Commandex.Shell that can execute them from unified shell.
- Calabonga.Commandex.Shell.Develop.Template → (
Tool Template) This is a Developer version of the Command Executer Shell (Calabonga.Commandex). Which is created to runs commands of any type for any purposes. For example, to execute a stored procedure or just to co… - Calabonga.Commandex.Engine → Engine and contracts library for Calabonga.Commandex. Contracts are using for developing a modules for Commandex Shell.
- Calabonga.Commandex.Engine.Processors → Results Processors for Calabonga.Commandex.Shell commands execution results. This is an extended version of the just show string in the notification dialog.
- Calabonga.CommandexCommand.Template → (
Tool Template) This is a template of the project to create a Command for Commandex. Just install this nuget as a template for Visual Studio (Rider or dotnet CLI) and then you can create a DialogCommand faster.
How to install template
Nothing is simpler then install this template. Just execute command in powershell:
dotnet new install Calabonga.Commandex.Shell.Develop.Template
How to use
This application tests your Command for Commandex in almost real conditions. Commands are discovered automatically: the shell scans its own output folder for assemblies and registers every AppDefinition / ICommandexCommand it finds. A few simple steps:
Install the template and scaffold a developer shell:
dotnet new install Calabonga.Commandex.Shell.Develop.Template dotnet new wpfshell -n Commandex.Developer.ShellImplement
ICommandexCommand(and itsAppDefinition) in a WPF Class Library project, then add a project reference to it fromCommandex.Developer.Shell. Its DLL now lands next to the shell on build.Set a real path in
commandex.env:COMMANDS_FOLDER="C:\Path\To\Your\Commands"Build and run the developer shell.
RegisterCommandsDefinitions()(inEngine/ServiceCollectionExtension.cs) scans the output folder and auto-registers all commands found, including the bundledSampleCommand. Pick one on the Executor tab and press Execute.The result is passed through
IResultProcessor(AdvancedResultProcessorfromCalabonga.Commandex.Engine.Processors), and a toast notification shows the outcome. Logs are written tologs/local-*.log(configured inApp).
Fallback — manual registration. If you do not want the folder scan, register the definition explicitly in Engine/DependencyContainer.cs:
// register all commands
services.AddDefinitions(typeof(YourAppDefinition));
Screenshot
v2.8.1
<img width="1183" height="774" alt="image" src="https://github.com/user-attachments/assets/c77116d5-198e-4438-8ab9-5b89564a61e7" />
v1.0.0
Ingredients
WPF, MVVM, CommunityToolkit, AppDefinitions, etc.
Видео (Video)
В основном репозитории Calabonga.Commandex.Shell есть несколько видео с инструкциями и разъяснениями, как использовать Commandex. А также видео о том, какие типы команд существуют и как для Commandex создавать команды разных типов.
-
net10.0
- No dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 5.0.1 | 35 | 9/2/2026 |
| 5.0.0 | 74 | 9/1/2026 |
| 4.0.1 | 543 | 12/5/2025 |
| 4.0.0 | 491 | 12/5/2025 |
| 3.0.1 | 736 | 7/26/2025 |
| 3.0.0 | 567 | 7/18/2025 |
| 2.8.1 | 538 | 7/12/2025 |
| 2.6.0 | 517 | 7/5/2025 |
| 2.5.0 | 546 | 6/29/2025 |
| 2.3.2 | 538 | 6/28/2025 |
| 2.3.1 | 578 | 6/20/2025 |
| 2.1.2 | 558 | 1/11/2025 |
| 2.0.0 | 547 | 11/19/2024 |
| 2.0.0-beta.1 | 486 | 11/19/2024 |
| 1.4.2 | 564 | 11/12/2024 |
| 1.4.1 | 572 | 11/1/2024 |
| 1.3.0 | 556 | 10/12/2024 |
| 1.2.0 | 556 | 10/9/2024 |
Aligned with Commandex Framework 5.0.1. The generated dev-shell references Calabonga.Commandex.Engine.Processors 5.0.1 and defines AppBackgroundBrush / TextSecondaryBrush in App.xaml as a DialogWindow customization example.