Ahh, I see. That makes a bit more sense. Your problem was that you kept thinking of Managed C++ as C++, which it's not really. It's VERY similar, sure, and that's the point, but it's still .NET rather than native. While I can certainly understand that you would like to reuse all that code you've written over the years, sometimes you have to realize that you're in a different world and do like the romans (to mix metaphors). I mean, would you have tried to reuse that code if you'd been programming in Java? Cobol? MC++ *IS* a different language, just like those are. Yeah, you can take a lot of your skills with you to help with the learning curve, but it's still going to be a learning curve. I too have built up a lot of experience with COM and MFC, largely to the point that I haven't used the wizards in years (other than AppWizard to generate a shell). MFC gives you a lot of power if you know it that well. However, the library available with .NET has dwarfed my benefit from MFC in my eyes. Stuff like DirectoryServices support, Extensive socket support (CSocket was always so lame), database support (DAO likewise, was lame and CRecordset worse). Yes, I too am sad to see MFC slowly die away, but I would consider that it lived a full life, and no technology lasts forever. -- Where are we going? And why am I in this handbasket?