Calabonga.Commandex.Engine
1.3.0
See the version list below for details.
dotnet add package Calabonga.Commandex.Engine --version 1.3.0
NuGet\Install-Package Calabonga.Commandex.Engine -Version 1.3.0
<PackageReference Include="Calabonga.Commandex.Engine" Version="1.3.0" />
paket add Calabonga.Commandex.Engine --version 1.3.0
#r "nuget: Calabonga.Commandex.Engine, 1.3.0"
// Install Calabonga.Commandex.Engine as a Cake Addin #addin nuget:?package=Calabonga.Commandex.Engine&version=1.3.0 // Install Calabonga.Commandex.Engine as a Cake Tool #tool nuget:?package=Calabonga.Commandex.Engine&version=1.3.0
Calabonga.Commandex.Engine
This is a nuget-package for modular monolith application on WPF platform with plugins as modules. Engine and contracts library for Calabonga.Commandex. Contracts are using for developing a modules for Commandex Shell.
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 → This is a Developer version of the Command Executer (
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.
History of changes
v1.3.0 2024-10-12
- The
SettingsPath
parameter was created to allow you to store the command's settings env-files in a separate folder - Summaries for some members were updated
v1.2.0 2024-10-09
- Nugets dependencies versions updated
ServiceCollection
extension created for DefaultResultProcessor registration in container- Base commands processing implementation updated for new type of the result creation available
IResultProcessor
interface created as abstraction for pipeline processing- Some classes and interface was renamed
- Some base commands property Result is marked as virtual
v1.1.0 2024-10-07
- Dialog window size management improved for ObservableValidator too. Now, you can set up a size of the dialog window.
v1.1.0-beta.1 2024-10-03
- Dialog window size management improved
v1.0.0 2024-10-01
- First Release
v1.0.0-rc.17 2024-09-28
ParameterCommandexCommand
getting parameter and setting parameter refactored. PropertyParameter
removed. For read data you can useReadParameter()
method. And for write -WriteParameter()
.- Some summaries added/updated
v1.0.0-rc.16 2024-09-16
- UX refactored
- Menu added
- Shortcuts added
- Three type of the command list view added
IDialogResult
renamed toIViewModel
- New property
Tags
added toICommandexCommand
for future commands groups management
v1.0.0-rc.15 2024-09-15
- Restart Wizard command crash fixed.
- NotificationDialog windows size fixed.
v1.0.0-rc.14 2024-09-14
- Main window MinHeight and MinWitdth are set
- Wizard window MinHeight and MinWidth are set
- Wizard window UX management properties make as virtual
- Some controls sizing improved
- Nugets dependencies updated
- Windows accent color is set for
ActiveStep
on Wizard dialog.
v1.0.0-rc.13 2024-09-13
- Nugets versions updated
OnSetParameter()
method created forIDialogResult
DialogService
implementation moved into engine nugetNotificationDialog
implementation moved into engine nugetWizard
component moved into engine nugetAppSettings
moved into engine nuget
v1.0.0-rc.11 2024-09-11
ShoeDialog()
added override with special parameter forViewModel
- Nuget feed URL moved into configuration parameters
v1.0.0-rc.3 2024-08-14
Реализован новый тип команды Wizard для Commandex. Теперь можно формировать набор шагов, которые проходит команда при в выполнении.
Обновлен также Shell для Developer, чтобы иметь возможность запускать новый тип команд.
v1.0.0-beta.9 2024-08-02
- Добавлена возможность управлять типом
Window
при отображении модального окна.
v1.0.0-beta.7 2024-07-31
- Первая публичная сборка в nuget
Видео (Video)
В основном репозитории Calabonga.Commandex.Shell есть несколько видео с инструкциями и разъяснениями, как использовать Commandex. А также видео о том, какие типы команд существуют и как для Commandex создавать команды разных типов.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net8.0-windows7.0 is compatible. |
-
net8.0-windows7.0
- Calabonga.Results (>= 1.1.0)
- Calabonga.Wpf.AppDefinitions (>= 1.0.0)
- CommunityToolkit.Common (>= 8.3.2)
- CommunityToolkit.Diagnostics (>= 8.3.2)
- CommunityToolkit.Mvvm (>= 8.3.2)
- DotNetEnv (>= 3.1.1)
- Microsoft.Xaml.Behaviors.Wpf (>= 1.1.135)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Calabonga.Commandex.Engine:
Package | Downloads |
---|---|
Calabonga.Commandex.Engine.Processors
Results Processors for Calabonga.Commandex commands execution results. This is an extended version of the just show string in the notification dialog. |
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
1.4.2 | 86 | 11/5/2024 |
1.4.1 | 81 | 11/1/2024 |
1.3.0 | 93 | 10/12/2024 |
1.2.0 | 86 | 10/9/2024 |
1.2.0-beta.1 | 48 | 10/9/2024 |
1.1.0 | 74 | 10/7/2024 |
1.1.0-beta.2 | 46 | 10/3/2024 |
1.1.0-beta.1 | 48 | 10/3/2024 |
1.0.0 | 93 | 9/30/2024 |
1.0.0-rc.17 | 45 | 9/28/2024 |
1.0.0-rc.16 | 74 | 9/16/2024 |
1.0.0-rc.15 | 49 | 9/14/2024 |
1.0.0-rc.13 | 60 | 9/13/2024 |
1.0.0-rc.12 | 50 | 9/13/2024 |
1.0.0-rc.11 | 59 | 9/11/2024 |
1.0.0-rc.10 | 54 | 9/10/2024 |
1.0.0-rc.9 | 58 | 9/5/2024 |
1.0.0-rc.8 | 47 | 9/5/2024 |
1.0.0-rc.7 | 57 | 9/4/2024 |
1.0.0-rc.6 | 50 | 9/4/2024 |
1.0.0-rc.5 | 77 | 8/20/2024 |
1.0.0-rc.4 | 67 | 8/16/2024 |
1.0.0-rc.3 | 76 | 8/14/2024 |
1.0.0-beta.20 | 60 | 8/7/2024 |
1.0.0-beta.17 | 33 | 8/5/2024 |
1.0.0-beta.16 | 32 | 8/5/2024 |
1.0.0-beta.13 | 36 | 8/4/2024 |
1.0.0-beta.10 | 41 | 8/2/2024 |
1.0.0-beta.9 | 39 | 8/2/2024 |
1.0.0-beta.7 | 39 | 7/31/2024 |
The SettingsPath parameter was created to allow you to store the team's settings in a separate folder.