We have a decent size MFC MDI desktop app. Is there a reasonable way to convert a MFC app to a .net app or is it better to just rewrite? If the answer is app specific, what criteria do you use to make the decision?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We have a decent size MFC MDI desktop app. Is there a reasonable way to convert a MFC app to a .net app or is it better to just rewrite? If the answer is app specific, what criteria do you use to make the decision?
I would skip WinForms and head right for WPF.
Depending on how your application is designed, you shouldn’t have to rewrite everything. You can call C++ code from C# code using Managed C++ wrappers, allowing you to reuse existing C++ code. Microsoft also has extensive documentation on interoperation between WPF and Win32/MFC. You can do similar things with WinForms.
Microsoft has gone to great lengths to provide migration paths from MFC to WinForms/WPF because they know companies can’t just throw away years of developed code.
Also, if you google ‘WPF and MFC’ you’ll find lots of examples of people using the two technologies in the same project.