One way to reuse I taught was (if possible, but I don't know how) to convert those .h/.cpp clas(ses) to an ActiveX control. May be creating a new MFC ActiveX DLL project, and then, through interop to access this ActiveX (COM object). But may be I'm saying a nonsense thing..

Hello, As you might know CodeGuru is an excellent web site were tones of controls and software in general is posted for free. For historical reasons the big majority of contributions are witten for MFC (VC 6.0), ATL, and alikes. If you surf it you'll colud find very valuable pieces of software. Most of them come in files .h and .cpp that integrate smoothly whith an MFC app. I would like to ask a question: Somebody knows a way or has tried to reuse this software from NET and C# using interop? Thanks, Josep L Colom

Yes COM exists and even Win32API exists under NET. But NET sets new paradigms in sofware design that enhances the COM approach. But NET doesn't need to have COM under it to work. Think in the MONO project (NET porting in Linux platform). As software users I think the NET class libraries should be our low level 'API' (even actually under it we can see COM influences, Win32 API calls, X86 staements, pipeline ALU microinstructions or transistors).

I recommend neither of those subjects. It's better go on with .NET and C# The Win32 API is old .. is not object oriented. It is deprecated .. even you can access it from .NET The MFC is a rich framework, but old as well. Even you can build great applications with it. ATL - based in templates - like STL, was great to build controls with small footprint, and to wrap COM. But COM is old .. now you have .NET WTL is a framework like MFC, but with the ATL philosophy. I recommend to stay only in .NET, and C#, as a new, more clean, less prone to error language than C++. This is also the Microsoft opinion. Josep L Colom