Perhaps we are on same quest I just posted this query. Please click here Although I may not have as much UNIX background as you do, I do approach problems in same manner of compartmentalization and what I am essentially attempting to do is implement an UNIX tee.

You'll need to download the additional content you want. VS 2012 --> Help --> Add and Remove Help Content This will start the Help Viewer 2.0 and open the Manage Content tab. Here you'll be able to download and update (or remove) content including .NET 4 (Available Documentation --> Additional Development Resources --> .NET Framework 4). Best regards D.C.

Richard, thank you. Very much! An excellent suggestion! However after a sleepless night (anybody know why stuff like this always happens on site during acceptance testing?) a good friend this morning showed me error of my ways. You, see, the only problem was I have a wretched case of idiotitis. In my zeal to explore the nooks and crannies of this Windows world I made the decision that a nice clean way to allow objects to get information from other objects was exposé an event and delegate. Seemed reasonable to me at the time. Having spent most of my life in a world where objects on different threads have REAL boundaries I assumed that if some object from another thread registered a handler that naturally when that handler was invoked from thread 2 that the event would interrupt thread 1 it would process the event and thread 2 would go merrily on its way. Nope. Thread 2 runs the event handler. Well when the thread that is minding your comms is now suddenly executing code in MainWindow which consists of putting up a dialog guess who isn't watching his comms. Error of my ways #2 has to do with where one starts threads, which is the point you are making. I was informed that launching critical long running tasks from the MainWindow code was not a very good idea. Suggestion was to move them to the App class and override OnStartup. Which I have now done. That does create several questions but I will save them for another day. Error of my ways #3 was to foolishly mentally assign characteristics to objects in threads as I would to a process of lightweight thread in other operating systems. Not a good analogy. Sorry for the length but somebody out there will make the same boo-boo someday. Thank you again, Doug I am a Traveler of both Time and Space

Good solution! I am using that in a couple of places and that helps. More I am trying to avoid a mix of EventWaitHandles and delegate/event handlers. I think this is a bit "messy" looking. But with schedule tight sometimes you just have to do what you have to do ;-) Doug I am a Traveler of both Time and Space

Good tip! Thanks i will look into this. I am using VS2010 so will need the add on. Doug I am a Traveler of both Time and Space

You can still use a message queue in C# hey! Write your own and test it! ;) There is one in the framework btw! http://msdn.microsoft.com/en-us/library/dd267265.aspx[^] My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!