哪个是Windows应用程序开发的更好方法以及原因：MFC或本机C / C ++编码。 [英] Which is the better approach to windows app development and why: MFC or native C/C++ coding.

问题描述

Windows应用程序开发真的是更好的方法：MFC或本机C / C ++ ciding？

Which is really the better approach to windows apps development: MFC or native C/C++ ciding?

推荐答案

你能编写一个单一的通用谓词 bool IsBetter（技术一，技术二）？我对此表示怀疑，因为几乎不可能定义什么是更好。更好的是什么？



这取决于目的。这两种方式对于应用程序开发来说都不是最简单的方法，但使用MFC可以自由组合两者。如果您想学习Windows，使用原始Windows API开发一些软件非常有用。即使您在MFC中执行所有操作，最好还是了解原始Windows API的工作原理。



MFC包含许多过时功能，特别是它可以兼得很好处理标准C ++库（STL，std :: *名称空间）模板/类但与当时不兼容，这只是一个相当大的烦恼。一般来说，MFC是旧的，生锈的，笨重的，丑陋的，也是专有的。有许多不同的C ++框架比MFC更优雅而不是专有，有些也是多平台，与MFC相比，更好的是非C ++框架和.NET。所以MFC将是我的最后选择。

-SA

Can you write one single universal predicate "bool IsBetter(Technology one, Technology two)"? I doubt it, as it's hardly possible to define what is "better". Better for what?

It really depends on the purpose. Both ways are not the easiest for application development, but with MFC you can freely combine both. If you want to learn Windows, it's very useful to develop some software using raw Windows API. And even if you do everything in MFC, it's better to understand how raw Windows API works.

MFC includes a lot of obsolescent features, in particular, it doubles a good deal of standard C++ library (STL, std::* namespaces) templates/classes but is not compatible with then, which is just a considerable annoyance. And generally, MFC is old, rusty, bulky and ugly, also proprietary. There are a number of different C++ frameworks which are more elegant and not proprietary like MFC, and some are also multiplatform, in contrast to MFC, set aside even better non-C++ frameworks and .NET. So MFC would be my very last choice.

—SA

我对你很困惑问题。

I am confused with your question.

您的问题：

MFC还是原生C / C ++编码？

MFC or native C/C++ coding?

我相信原生C / C ++你的意思是原始的Win32 API。我一直认为MFC和Win32是原生的，而.Net要管理。我猜你还没有学过MFC和Win32。所以我建议你先学习Win32 API然后再转到MFC。然后你会明白哪个更适合给定的目的。



如果你先学习Win32 API，那么转移到MFC将非常容易。这样，您将了解有关操作系统如何工作的更多信息。 这是一本了解Win32 API的好书。

I believe by "native C/C++" you meant the raw Win32 API. I have always considered MFC and Win32 to be native and .Net to be managed. I guess you haven't learned neither MFC nor Win32. So I advice you to first learn the Win32 API first and move onto MFC. Then you will understand which is better for a given purpose.

If you learn Win32 API first, moving onto MFC will be very very easy. This way you will understand more about how an OS works. This is a great book to learn the Win32 API.

你好GbemBam，



你无法比较两种技术。每种技术都有自己的优点和缺点。

我也正在学习Windows应用程序开发如果你不想开发需要非常敏锐的硬件通信的游戏和/或应用程序，那么我会遇到一个结果可以继续使用您选择的任何oop语言。但是当谈到传感器，GPS等硬件接口时，你应该使用C ++。

Hello GbemBam ,

You can not compare two technologies. Every technology have its own pros and cons.
I am also studying windows app development i come across a result if you are not trying to develop game and/or application that needs a very sharp hardware communication then you can proceed with any of oop language of your choice. but when it comes to hardware interface like sensors, GPS etc you should go with C++.

这篇关于哪个是Windows应用程序开发的更好方法以及原因：MFC或本机C / C ++编码。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！