blocks|key|1623676|text|内存占用。但是，除非您正在为内存严重不足的机器进行开发，否则对于大多数应用程序来说，这真的不应该是问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1623677|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Memory footprint. But unless you're developing for a severely handicapped machine memory-wise, it really shouldn't be an issue for most applications.

blocks|key|1623717|text|如果您的应用程序需要能够在没有安装的情况下运行(例如，如果您不能或不应该执行诸如安装.NET框架之类的操作)，则不能指望.NET运行在windows计算机上(Vista之前的版本)。很多实用程序都属于这一类。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1623718|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If your application needs to be able to run without an installation (i.e. if you can't or shouldn't do something like install the .NET framework), you can't count on .NET being on a windows machine (pre-Vista). Lots of utility applications can fall in this category.

blocks|key|1409098|text|对于小型可下载应用程序来说，最重要的一点是本机代码不需要.NET运行时。虽然宽带变得越来越普遍，但并不是每个人都有宽带。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1409099|有些人可能会失望地看到，您的2MB应用程序实际上需要另外20MB的框架下载和麻烦的安装过程才能运行。如果他们一开始就不确定是否真的需要你的应用程序，他们可能会在尝试之前就把它删除，然后转向一个竞争产品。|1409100|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

IMO the most important one for small downloadable applications is that native code does not need the .NET runtime. While broadband becomes more and more common not nearly everybody has it yet. 

Some people may be disappointed to see that your 2 MB application actually requires another 20MB of framework download and a bothersome installation process to run. If they are not sure whether or not they really need your application in the first place, they might just delete it before even giving it a try and turn to a competing product.

blocks|key|1623812|text|如果你能负担得起对堆栈的依赖，那就选择.NET现代，优雅，强大，因此开发起来要快得多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1623813|但要意识到，你的应用程序与语言和框架联系在一起，如果你预见到未来你可能想要摆脱这一点，那么最好三思而后行。|1623814|Win32既旧又笨重，但它几乎可以在任何Windows版本上运行，没有额外的依赖，并且您的代码可以是普通的、可移植的、C/C%2B%2B。|1623815|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

If you can afford the dependency on the stack, go for .NET
Modern, elegant, powerful and as a result much quicker to develop for.

But realize that you chain your app to it - to the language and the framework, if you forsee a future where you may want to escape this, then better think twice.

Win32 is old and clunky, but it works on virtually any Windows version without extra dependencies, and your code can be in plain, portable, C/C++.

blocks|key|1623845|text|%2B1表示不需要在目标计算机上安装.NET软件包。这仍然是一个大问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1623846|当所有机器都有单声道或网络时，这就不是什么大问题了。|1623847|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

+1 for not having to require a .NET package/install on the target machine(s). This is still a big issue.

When all machines have mono or NET it won't be such a big deal.

blocks|key|1409219|text|.Net程序也有支持生命周期，而本机程序没有。Native可以在不同的操作系统上运行很多年，不需要更新。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1409220|糟糕的.Net配置可能会淹没.Net程序，本机程序只会继续运行，几乎不会受到操作系统更新的影响。|1409221|.Net程序启动慢，感觉慢，本机启动快，运行快。|1409222|.Net必须编码为最小公分母(大多数分布式框架版本)，本机将所有代码编译成应用程序-所以请使用您想要的。|1409223|使用本机的Delphi，而不是C%2B%2B。.Net部分基于Delphi+RAD和Java后端。|1409224|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

.Net programs also have a support lifetime, where native do not really. Native will run for many years across different OS's without requiring updates.

.Net programs can be hosed by bad .Net configuration, native just keeps on running and is hardly effected by OS updates.

.Net programs startup slow and feel sluggish, native starts quick and runs quick.

.Net has to be coded for lowest common denominator (most distributed framework version), Native compiles all code into application - so use what you want.

Use Delphi for Native, not C++. .Net is partially based on Delphi RAD and Java backend.

I learned windows programming using Visual C++, and the Win32 API. Nowadays, it seems most apps are being developed in .NET using C#. I understand that most of the time there isn't much performance difference between native code and managed code. So I'm wondering, if I were to start writing a new desktop app today, is there any reason (other than the fact that I'm more familiar with C++), that I might want to write it in non-managed C++ instead of .NET? Are there still some advantages to using C++ and native code? Or has that method been more-or-less replaced with .NET on the Windows platform? 

Of course I know that people who are writing low-level device drivers and similar programs wouldn't do it in .NET. I'm asking with reference to typical client-facing apps that don't make direct hardware calls.

What advantages are there to developing a Win32 app in C++ over a .NET app in C#?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我学习了使用Visual和Win32 C++进行windows编程。如今，似乎大多数应用程序都是使用C#在.NET中开发的。据我所知，大多数情况下，本机代码和托管代码之间没有太大的性能差异。所以我想知道，如果我现在开始编写一个新的桌面应用程序，有没有什么原因(除了我更熟悉C++)，我可能想要用非托管C++而不是.NET...

问与在C#中开发.NET应用相比，在C++中开发Win32应用有哪些优势？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问与在C#中开发.NET应用相比，在C++中开发Win32应用有哪些优势？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问与在C#中开发.NET应用相比，在C++中开发Win32应用有哪些优势？
EN