WinRT 上的 C++、C# 和 JavaScript

.NET (C#/VB) - mid-level, statically typed with optional dynamic typing (dynamic keyword etc) and GC. XAML UI framework is the default one for UI, but you can also use HTML by using WebView control. Provides full access to WinRT libraries, but also some of its own on top of that, which are sometimes more convenient to use (e.g. Stream vs IInputStream/IOutputStream). Also, the only one that includes special language-level support for asynchronous operations (async and await keywords), which are used heavily when using WinRT APIs due to their highly asynchronous design. Generally speaking, provides most syntactic sugar - aside from async stuff, you get LINQ to objects (which works over WinRT collections). Can write your own WinRT components, which can then be used from JS or C++/CX. Existing .NET libraries may or may not be readily reusable, depending on what classes in .NET Framework they rely on; components written for Silverlight or WP7 are most likely to be reusable with no or minimal changes, while components written for .NET 4 Full or Client Profile may require significant changes to run.

C++/CX(Visual C++ 组件扩展) - 低/中级，静态类型，无 GC - 仅引用计数.最接近金属"，因为它的对象模型被设计为直接映射到 WinRT，没有阻抗不匹配——因此是引用计数——但仍然足够高级，可以避免样板文件并且通常可以安全使用(例如，异常而不是 HRESULT，看到的字符串作为对象而不是句柄，dynamic_cast 而不是 QueryInterface 等).您和 WinRT 之间没有额外的层、代理对象等，所有调用都是直接的.在大多数情况下，这三者中最快的，尽管确切的差异取决于具体任务而有很大差异，并且对于某些(例如，没有或很少计算的事件驱动应用程序)来说可能是微不足道的，而对于其他人(例如解析或繁重的数学)来说可能是相当大的).UI 故事与 .NET 相同.此外，您还可以获得整个 C++ 标准库，以及 ATL 的一个子集.可以编写自己的 WinRT 组件，然后可以从 JS 或 .NET 中使用.现有的 C++ 库可能容易重用，也可能不容易重用，这取决于它们使用的 API；那些严格依赖标准 C/C++ 的应用程序通常无需更改即可工作，而那些调用 Win32 API 的应用程序如果依赖于 Metro 应用容器中不可用的 API，则可能会出现问题.

C++/CX (Visual C++ Component Extensions) - low/mid-level, statically typed, no GC - refcounting only. Closest "to the metal" in that its object model is designed to map directly to WinRT with no impedance mismatch - hence refcounting - but still high-level enough to avoid boilerplate and be generally safe to use (e.g. exceptions rather than HRESULTs, strings seen as objects and not handles, dynamic_cast rather than QueryInterface etc). No additional layers, proxy objects etc between you and WinRT, all calls are direct. In most cases, fastest of all three, though the exact difference varies significantly depending on the specific task, and can be minuscule for some (e.g. event-driven app with no or little computation), and considerable for others (e.g. parsing or heavy math). UI story is same as for .NET. In addition, you get the entire C++ standard library available to you, as well as a subset of ATL. Can write your own WinRT components, which can then be used from JS or .NET. Existing C++ libraries may or may not be readily reusable, depending on which APIs they use; those that relies strictly on Standard C/C++ will usually work with no changes, while those that call Win32 APIs may pose a problem if they rely on APIs not available in Metro app container.

关于#3，这个视频 - http://channel9.msdn.com/Events/BUILD/BUILD2011/TOOL-789C - 应该回答您关于 Metro 应用程序中使用 Win32(我认为是低级 DLL"的意思)的大部分问题.请注意，虽然视频是关于 C++ 的，但这也完全适用于 C#，因为 P/Invoke 和 COM 互操作仍然存在.因此，如果您可以从 C++ 调用它，那么您可以从 C# 调用它.

Regarding #3, this video - http://channel9.msdn.com/Events/BUILD/BUILD2011/TOOL-789C - should answer most of your questions regarding the use of Win32 (which I presume what "low-level DLL" means) from Metro apps. Note that while the video is about C++, this also fully applies to C#, as P/Invoke and COM Interop are still there. So if you can call it from C++, you can call it from C#.

这篇关于WinRT 上的 C++、C# 和 JavaScript的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持编程学习网！