Objection to the MVVM template - lack of IDE support - does any of the frameworks help?

Question

Some of our developers do not like the team in MVVM because there is no support in the VS2010 IDE to help you move from the Command binding in xaml to the actual code that implements the behavior. Using the code, you can right-click and select "Move to event handler." We start a new project with 4 developers, but we usually divide the work into functional areas, rather than Ux and business logic, so each developer works in xaml and viewmodel / domain to implement the necessary functions.

Do you guys consider this a hindrance to adopting MVVM?

Does any of the frameworks help in this regard?

Are there any tips / tricks that make this navigation easier?

Perhaps we should try to split the work between Ux and application logic?

Thanks for any ideas.

Answer 1

It sounds like nagging to me, not actual criticism of commands or MVVM. It does not require much effort to implement and use MVVM. I have never used a framework to implement MVVM.

I always put my commands at the top of my viewmodel classes, and then public properties, constructor and functions.

If you cannot find them in your view model, your file may be too long. Is it over 1,500 lines? If so, consider splitting into several classes.

Answer 2

None of the frameworks help in this problem, since it is usually not a problem. If you want to use MVVM, I would suggest redesigning the command so that the work is divided as MVVM suggests.

I work mainly in virtual machines and I have never had a problem with XAML .... because I almost never touch it. The converse is true for our guy who is developing our views. It works almost completely in XAML and does not write much code in C #.