This 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.
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 (plugins) from GUI.
Get the results of the module's (plugins) 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.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.
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:
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.
v2.2.0 2025-04-15
Engine nuget: Open dialog in the window maximized now available. See the override for DialogResult IsMaximized
Some refactoring made, syntax error fixed.
v2.1.0 2025-01-30
Identity abstraction added (Engine package)
v2.0.1 2024-11-21
More info shown on ClipboardResult processing competed.