A reader of my Silverlight 5 book recently reached out tome about threading and why I create some objects on the UI threadin the examples. We discussed some of the reasons, but I felt thiswould be a good topic to share with everyone. In fact, this is onearea where it would have been fun to go into great detail in mybook, but there simply wasn't the space. Threading and cross-threadexceptions can be a bit of a mystery to new Silverlight and WPFdevelopers.
BackgroundThe user interface in Silverlight runs on a thread commonlyknown as the UI Thread. Any code you create in the code-behind, andany code it calls all the way down the chain, unless it explicitlycreates another thread, runs on this same UI thread. It's not atall uncommon to see Silverlight and WPF applications which neverexplicitly create a second thread, but do make calls to otherservices which create background threads for processing.
There are man ...
Go to the complete details ...