CODEWITHSUNDEEP
c++visual-studio-2010mfc
diwatu
diwatu

Reputation: 5699

Which toolkit should I convert my existing MFC project to?

I have a quite big MFC project all with unmanaged C++ code and MFC GUI. From

What's new in Visual Studio 2013 for native development,

ATL and MFC changes and fixes in Visual Studio 2013

I know MFC was never ever dying as fast as now.So I have to start to consider where my project should go, in other words, what I should convert my project to, I have to do this sooner or later.

If I start a new project form scratch, I know the alternative would probably be QT, but the question is also, if I want to do so, how could we convert the code to QT?

Upvotes: 0

Views: 306

Answers (1)

Max
Max

Reputation: 3180

Questions to ask yourself or your boss or manager:

Is it worth the time and money to convert your application? Will you be paid to do that ? will it bring extra revenues to you and/or your company ? Can you spare weeks of re-factoring for a new framework without working on other issues and improvements that will bring in more money to you ?

Do you have any deal-breaker or critical issues with the current MFC and C++ implementation that you have to fix or workaround ? Most issues can be worked around

Are there features in other toolkit that you cannot live without ? Do you feel like you are always re-inventing the wheel for basic features that are already supported by other toolkits?

Upvotes: 2

Related Questions