Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • You should use whichever tool makes the task simple. There's nothing at all wrong with writing code... seriously. Commented Sep 1, 2012 at 19:38
  • In my opinion.. it IS! When I decided to work with MVVM I don't want to mix. Only code behind.... or only mvvm.. but no mix. I think this is important. Commented Sep 1, 2012 at 19:45
  • Why do you think that is important? Commented Sep 1, 2012 at 19:51
  • 1
    Code-behind has its purposes, you know. MVVM doesn't mean no code-behind. It means removing code from the code-behind that shouldn't be there. Commented Sep 1, 2012 at 19:57
  • 1
    "70% in viewmodels and 30% code in code behind it's harded for you get into the application." - Sounds to me like an uninformed assumption. I have no problem reading code, no should any software developer. MVVM is about separating the presentation from the logic. That doesn't mean the logic goes away entirely. This all sounds very dogmatic. each situation is different, you do your best to create a maintainable application given your requirements. Commented Sep 1, 2012 at 20:41