3 ms·
«And what are we meant to do with this 2 million+ lines of MFC codebase we have? What future does MFC have? There is silence on the matter. All in all it doesn'
by WorldMaker 10y ago
«And what are we meant to do with this 2 million+ lines of MFC codebase we have? What future does MFC have? There is silence on the matter. All in all it doesn't instill confidence at all.»
Wasn't MFC deprecated in favor of ATL a long time ago, and that in turn deprecated in favor of WTL? All three of which now seem deprecated in favor of C++/Cx. I haven't kept up with C++ that well, but I don't think MFC has had a future for a long time. I don't think Microsoft has been that silent on it either, albeit the communication has shifted and evolved over the years as Microsoft settled their COM/.NET/UWP approaches...
What you could do with that codebase today is use the Desktop App Converter to wrap it in a UWP package (.appx). Once converted you could also slowly start to migrate to C++/Cx and UWP APIs and XAML screens. There are a bunch of Microsoft blogs about that if you wanted to read more.
- 72deluxe 10y agoAs it turns out, this problem is really my employer's problem. I suspect many other software vendors have the same problem with these festering codebases. Hopefully my employer will being making moves to other frameworks some time soon (and first things first off C++2003)...