Скачать или смотреть Using a Single DelegateCommand with Multiple Parameters in Prism

Learn how to effectively use a single `DelegateCommand` in Prism to handle multiple button commands by passing parameters seamlessly in high-level WPF applications using MVVM design.
---
This video is based on the question https://stackoverflow.com/q/64446153/ asked by the user 'DelusionX' ( https://stackoverflow.com/u/14456332/ ) and on the answer https://stackoverflow.com/a/64446474/ provided by the user 'Clemens' ( https://stackoverflow.com/u/1136211/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Pass three parameters to Prism DelegateCommand to use the same command on different button commands [MVVM mode]

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Efficiently Using a Single DelegateCommand with Multiple Parameters in Prism

When working with the Prism library in a WPF application, you might need to handle multiple button commands while minimizing code duplication. This can be challenging if you want to utilize the same command logic across different buttons but with varied parameter inputs. In this post, we’ll explore how to accomplish this using DelegateCommand and how to pass parameters dynamically to streamline your MVVM (Model-View-ViewModel) structured application.

The Problem

You have the following setup in your ViewModel using DelegateCommand:

[[See Video to Reveal this Text or Code Snippet]]

In your XAML, you have bound this command to a button:

[[See Video to Reveal this Text or Code Snippet]]

You want to extend this functionality to two additional buttons without creating new command instances (like MyButtonClickCommand1 or MyButtonClickCommand2). This is where the challenge lies in passing parameters effectively through your commands.

Solution Overview

To solve this issue, you can define a custom command parameter class that holds the necessary data you wish to pass to your command. Doing so allows you to send in multiple types of parameters in a clean and organized manner without cluttering your ViewModel.

Step 1: Create a Command Parameter Class

Define a class that represents the structure of the command parameters you need. For example:

[[See Video to Reveal this Text or Code Snippet]]

This class will encapsulate the parameters you want to pass to your command.

Step 2: Modify Your XAML to Use Command Parameters

In your XAML, you can now bind the command and pass an instance of MyCommandParameter. Here's how you can do it for multiple buttons:

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Update the Command Execution Logic

Update your command execution method to handle the parameter received from the buttons. You’ll modify your FuncToCall method to extract information from the passed parameter:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

Using a single DelegateCommand helps maintain cleaner and more manageable code in WPF applications following the MVVM pattern. By introducing a parameterized class, you can effectively pass different values dynamically to a single command handler. This technique not only reduces redundancy but also enhances the maintainability of your codebase.

Now, you are equipped with a structured way to utilize DelegateCommand while efficiently managing your button commands in Prism. Happy coding!