Yes, at first I thought I was imagining it (VS 2005 and the end of dll hell, etc. etc. :)). Since I believe that mmPicker is a composit class, it makes no sense to me that only mmPicker was affected. I have not inspected the dll for namespace conflicts and probably won't unless I absolutely have to use it.

Since I am still thrashing around with VS and C#, it's entirely possible that I hosed it; but as mentioned, the perceived cure was to remove the 3rd party dll.