First of all, the main topic of the quesiton has nothing to do with WPF or any other UI, could be done with any.
More importantly, this is quite possible and would
totally defeat the purpose of multithreading. More exactly, it would be equivalent to 1 thread instead of 100, when this 1 thread simply consequently call the body methods of those 100 would-be-threads, one at a time. There will be one difference: 1 thread would do it faster then 100, by an apparent reason: considerable overhead of creation and initialization of a thread execution. The idea can be implemented but makes no sense at all.
As to using threads in WPF, you might need to learn one thing. As you can only call any methods or properties related to the currently executing UI through only one, UI thread, and other threads cannot do it, you would need to know
invocation technique which delegates the execution of UI-related code to UI thread, which is done via
System.Windows.Threading.Dispatcher.Invoke or
System.Windows.Threading.Dispatcher.BegingInvoke. Please see:
http://msdn.microsoft.com/en-us/library/system.windows.threading.dispatcher.aspx[
^].
Please also see my past answers:
Control.Invoke() vs. Control.BeginInvoke()[
^],
Problem with Treeview Scanner And MD5[
^].
—SA
Submit an article or tip