Results Processors for Calabonga.Commandex commands execution results. This is an extended version of the just show string in the notification dialog.
License
—
Deps
1
Install Size
—
Vulns
✓ 0
Published
Dec 5, 2025
$ dotnet add package Calabonga.Commandex.Engine.ProcessorsThis is a nuget-package for modular monolith application on WPF platform with plugins as modules. Results Processors for Calabonga.Commandex.Shell commands execution results. This is an extended version of the just show string in the notification dialog.
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:
.dll (plugins) in the folder you set up..dll (plugins) from GUI.It's a complex solution with a few repositories:
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…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.Calabonga.Commandex.Engine package updated. New type of the CommandexCommand added. ZoneCommandexCommand<TView,TViewModel> can be shown in a Shell Window in the special ContentControl marked as MainZone.Calabonga.Commandex.Engine package updatedCalabonga.Commandex.Engine package updatedCalabonga.Commandex.Engine package updatedCalabonga.Commandex.Engine package updatedIsPushToShellEnabled is false. Only logger save results in this case.Toast Notifications added into a Calabonga.Commandex.Engine. Please use How To Toast Notifications on the Engine repository.
Main dependency Calabonga.Commandex.Engine was updated. There are changes. ViewModelLocationProvider and ViewModelLocation created for Views and ViewModels binding automation. If you want to use AutoBindingViewModel on the View (XAML), something like shown below:
<UserControl x:Class="Commandex.MyDemoCommand.Views.MyDemoView"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
xmlns:local="clr-namespace:Commandex.MyDemoCommand.Views"
xmlns:viewModels="clr-namespace:Commandex.MyDemoCommand.ViewModels"
+ xmlns:viewModelLocator="clr-namespace:Calabonga.Commandex.Engine.ViewModelLocator;assembly=Calabonga.Commandex.Engine"
+ viewModelLocator:ViewModelLocator.AutoBindingViewModel="True"
mc:Ignorable="d"
d:DesignHeight="450" d:DesignWidth="800">Than you should initialize ViewModelLocationProvider in your Shell project in the Composition Root of your Application. For example:
var buildServiceProvider = services.BuildServiceProvider();
ViewModelLocationProvider.SetDefaultViewModelFactory(type => buildServiceProvider.GetRequiredService(type));
return buildServiceProvider;You should also follow the naming rules for Views and ViewModels (or create your own overrides). What's the rule? Everything is simple. For example, if your have a view with name PersonProfileView.xaml than you should create a ViewModel for it with name PersonProfileViewModel.
IsMaximizedClipboardResult processing competed.Calabonga.Commandex.Engine updated NET9Calabonga.Commandex.Engine updated where new ConfirnationDialog added (Func too).Calabonga.Commandex.Engine updated where new ConfirnationDialog added.SettingsPath parameter was created to allow you to store the command's settings env-files in a separate folderTextFileResult and ClipboardResult processors created.