Convert a large MFC application to .net

We have an MFC MFC app for a decent size. Is there any reasonable way to convert an MFC application to a .net application, or is it better to just rewrite it? If the answer is application specific, what criteria do you use to make the decision?

+3
source share
5 answers

I would skip WinForms and head straight for WPF.

Depending on how your application is developed, you do not need to rewrite everything. You can call C ++ code from C # code using Managed C ++ wrappers, which allows you to reuse existing C ++ code. Microsoft also has extensive documentation on the interaction between WPF and Win32 / MFC. You can do such things with WinForms.

Microsoft has gone long distances to provide migration paths from MFC to WinForms / WPF because they know that companies cannot simply throw away years of developed code.

In addition, if you use Google WPF and MFC, you will find many examples of people using two technologies in one project.

+2
source

MFC WinForms , -, - ++, # ( , ).

MFC, - #, ++ # , .

, , , , MFC .

MFC -, .net, , .

+1

, , , MFC .NET-, . Windows Forms, Win32, MFC.

MFC -, ++.NET , , , , # .

0

. , , .

0

#, WPF, Expression Blend, MVVM MFC WPF.

WPF (VS 2010) , 50% MFC , , . MDI.

MVVM , .

: , , XAML .

MFC, ( Expression Blend), , .

, MFC WPF/.NET - ; .

Do not drop Microsoft MFC or you will have people jumping from a ship. (WTF ?????)

-2
source

Source: https://habr.com/ru/post/1703352/


All Articles