Objection to MVVM pattern is lack of IDE support - do any of the frameworks help with that?

Some of our developers don't like the commanding i开发者_如何学运维n MVVM because there is no support in VS2010 IDE to help you navigate from the Command binding in xaml to the actual code implementing the behavior. With code-behind, you can right-click and select Navigate to Event Handler. We're starting a new project with about 4 developers but we typically divide the work into functional areas, not Ux and business logic so each developer is working in the xaml and the viewmodel/domain to implement the functionality needed.

Do you guys consider this a hindrance to adoption of MVVM?

Do any of the frameworks help in this regard?

Are there any tips/tricks that facilitate that navigation need?

Maybe we should try splitting work between Ux and app logic?

Thanks for any ideas.

---

Sounds like whining to me, rather than actual criticism of Commands or MVVM. It doesn't take much effort to implement and use MVVM. I haven't ever used a framework to implement MVVM.

I always put my Commands at the top of my viewmodel classes, followed by public properties, the constructor and functions.

If you're having trouble finding them in your viewmodel, maybe your file is too long. Is it over 1500 lines? If so consider breaking it up into multiple classes.

---

None of the frameworks help with this problem because it's not usually a problem. If you want to use MVVM, I would suggest reworking the team so that the work is split the way that MVVM suggests.

I work primarily in VMs and I never have any trouble with XAML. ...Because I almost never touch it. The inverse is true for our guy who designs our views. He works almost entirely in XAML and doesn't write much C# code.