- Share
- Description Click to Edit
-
John Gossman has blogged several times about the M-V-VM pattern for developing WPF applications. We've been using a similar pattern on the Max team, with slightly different terminology (DataModel instead of ViewModel). I thought I'd do a series of posts about some of our learnings here. With this pattern, you can make a well componentized application that cleanly separates the visual style from the behavior and makes the behavior code highly testable.
I know this post will probably bring in some comments about terminology. I'm just using the terminology we use on our team and it works well for us. Use whatever you like!
- Original URL Click to Edit
Comments
- threads
- flat
| Shared or Added By | To | When | Comments |
| Ryan Riley | .NET | 4 months ago | 0 comments |
| Ryan Riley | Windows Presentation Foundation | 4 months ago | 0 comments |
Tell me about Twine
Twine is convenient, new, powerful, smart, and totally devoted to whatever you're interested in. Read all about it.