Question

I’m working in a WPF project, I’m using the MVVM patter in my project.

I created a user control (also in WPF) and I want to use it in my project, now, my problem is that I have a method in my user control that I need to call from my View Model, but I don’t know how to do that, how to bind to the method inside my control from the view model.

If I use code behind, obviously there is no problem since I have a direct reference to my control, so I can do “mycontrol.MyMethod();”m, but of course, doing in this way will go against the logic of the MVVM pattern.

I tried to use a Dependency Property in my user control, and use that Dependency Property to bind to it in the xaml of my project but it didn’t worked, the compiler says that the property was not found or is not serializable.

So I will appreciate if someone can share some light about how can I accomplish this.

Edited

As far as I understand you have the view, which is all the GUI, then you have the model, which is all the logic, and them you have the view-model which is like an intermediate layer used to bind the view with the model, right?

In this way I have developed my project, however I came to the problem that I need a custom control, a TextBox that remember what the user entered, and when he start typing, if there are words that start with that letter, those words are shown as a suggestion, as Google does it.

This TextBox is used as a search filter; so I created a user control to do this, I added a method to my user control to allow whatever application that uses my control to add items to an internal array that holds all the strings that the user has entered.

I created a user control because I couldn’t find any control that behaves the way I want.

So my problem is when I add my user control to the main project, because I need to someway be able to call the method that add the items to the internal array, but maybe I’m doing things the wrong way, so if any of you has a better idea, I will appreciate if you shared it with me.

Answer 1

Why does the consumer of the user control need to maintain the control’s internal array? That seems like you’ve exposed an implementation detail that you don’t need to.

Why not simply make that array a dependency property (and an IEnumerable<string> or ObservableCollection<string> besides)? Then you can simply create the corresponding property in your view model and bind it to the control. It also makes the control considerably more versatile.