   MFC vs C# Winforms
  Hi,I have an application that does some fairly intensive CPU-centric processing in C++ using SSE extensions. I want to create a GUI interface to this backend, but I wanted your opinion on whether to use MFC or C# Winforms. I have used both and believe (as most of you will) that winforms is much easier. However, I haven't used P/Invoke much (since the C++ code is in a DLL) and wonder if it's worth the hassle.Many thanks for your input,MrCoolsman   
  P/Invoke is pretty straight forward once get your head around marshalling structures and strings, but you could also write a C++/CLI wrapper dll for your existing dll and call that directly from a C# based WinForms app.   ;  I think it'll take you much less time using P/Invoke to call your DLL from C# than using MFC to create your GUI from C++.  Therefore, I suggest you go the C# route.   ;  Choice N1: WinForms, C#, P/Invoke.Choice N2: WinForms, C++/CLI. Only one minus - dependency from MSVCRT dlls.   