WPF Twitter client with Model-View-ViewModel Design Pattern step by step

Introduction

This article details real world example of how to use a Model-View-ViewModel Design Pattern. I split the process of development into steps. Each step is based on the previous one and adds some specific functionality. At the end of each step we will have a working application.

As the example I chose Twitter Client. I suppose it is comprehensible and useful. I’ll use TweetSharp library to make work with twitter API simple and not cumbersome.

The reader is supposed to have some experience of work with WPF, in particular, having investigated data binding.

I will not write here why you should use MVVM while working with WPF. Yet if you want to read in details about motivation for using this design pattern, I recommend to you to read the article “WPF Apps with the Model-View-ViewModel Design Pattern” by Josh Smith. On my part I would like to say that design which smells is big pain, especially if you use WPF.

Background

A Twitter Client shows tweets grouped according to some criteria. It also allows submitting user’s tweet and send direct messages. Finally, it provides friends management – a user can “follow” somebody which means he or she will see the followings tweets in his or her tweetlist.  

We start off with looking at an existing Twitter Client before writing code. This analysis will clarify how our client should look and what controls we should use.

Read more: Codeproject

Posted via email from .NET Info