MVVMCross How does this View get linked to the ViewModel?

Question

I'm trying to figure out why I get an error message about not being able to find the right ViewModel when I'm running my iOS app.

The question I have is when I look at this example I don't understand where MainMenuView gets bound to MainMenuViewModel.

Can someone answer this for me?

Thanks,

PkL728

score 9 · Accepted Answer · answered Jul 11 '13 at 19:54

9

They are bound by class names: for XXXView should be corresponded XXXViewModel

answered Jul 11 '13 at 19:54

Roman Kagan

464
1
3
12

So in my iOS project I have a ProductsView class which extends MvxTableViewController and in my core project I have a ProductsViewModel class. When I run my program I get this error: Failed to load ViewModel for type LoginProductsMVVM.Core.ViewModels.ProductsViewModel from locator MvxDefaultViewModelLocator... Do I have this set up wrong? – PkL728 Jul 11 '13 at 19:56
Ok... so my error was related to a method being called in my ProductsViewModel constructor that was erroring out. Not a helpful error message!! Thanks Roman! – PkL728 Jul 11 '13 at 20:09
2

Make sure you have trace turned on - http://stackoverflow.com/questions/17233922/mvvmcross-mvx-trace-usage/17234083#17234083 - then you'll see more of the 'not helpful' error message. – Stuart Jul 11 '13 at 21:19
OMG. Wasted 2 days due to this. – GeneCode Mar 30 '17 at 05:28
Name convention is the default setting. There are several ways to override it: https://www.mvvmcross.com/documentation/fundamentals/Customizing-using-App-and-Setup#overriding-view-viewmodel-associations – Felix Oct 06 '17 at 04:35

score 1 · Answer 2 · answered Jul 08 '14 at 20:33

1

Just want to add to the answer: double-check the names of the views after renaming (even Resharper renaming is not perfect). Spent several dozens of minutes (and a beer can), catching similar MvvmCross's error Could not find view for %ViewModelName%.

answered Jul 08 '14 at 20:33

Vitalii Vasylenko

4,776
5
40
64

score 1 · Answer 3 · answered Apr 12 '16 at 20:00

I'm getting this on a project that I've just upgraded to MvvmCross 4. I don't have much experience with MvvmCross, and the project hasn't been maintained for a few years, so it's possible something else is wrong.

I ended up hard coding the mappings in Setup::InitializeViewLookup because I don't have time to waste on it anymore.

score 1 · Answer 4 · answered Jun 24 '16 at 01:50

For anyone who ends up here having the same problem I had. I was getting this error in an Android project because my (properly named) view was extending Activity and not MvxActivity (happens easily when you use Xamarin Studio's "Add Android Activity" feature)

MVVMCross How does this View get linked to the ViewModel?

4 Answers4