Hi friends,
In my career I had come across many good looking desktop application in which user do some click or tap his/her figure on screen for certain task and it becomes “not responding status” due to long running tasks. This type of Painful user experience makes application unsuccessful.
Means responsiveness of your application make difference. Hence developer should use threading in their application with some care to make more responsive application. In older .net (winform ) we have background work and threadpool to do threading. Now in WPF we got another feature named dispatcher which makes your threading work more easy hence you can make your WPF application better when you have long running task in you WPF screen .
Long-running processes are involved—whether getting large results from a database, making async Webservice calls, or any number of other potentially intensive operations makes our application more unresponsive so we need to make it responsive to make your end users much happier in the long run. But before you can start using an async programming model in your WPF app, it is important that you understand the WPF threading model. In this blogI will not only introduce you to that threading model, but I'll also show you how the Dispatcher-based objects work and explain how to use the BackgroundWorker so that you can create compelling and responsive user interfaces(i will do in next blog)