We are using legacy SSL COM .NET wrapper classes in our apps and I'm trying to unit test some new functionality. I can test my functionality if I create a new Windows App, set the appropriate callback functions, and call the "start" method on the ssl record. However, if I do the same thing in either a console app or in a Unit test running under Visual Studio Testing framework, I can't get the the ssl libraries to call my callback functions. I believe it has something to do with the Windows message pump and how it executes (or doesn't) in a Console App and in a Visual Studio testing app. Can you point me to some information on how the threading model or the record update model works with the message pump so I can implement my tests correctly? if you have examples of unit tests, better yet.