精通C++/CLI：Visual C++程序员的.NET指南

需积分: 9 75 浏览量更新于2024-07-29 1 收藏 2.56MB PDF 举报

"Expert C++/CLI: .NET for Visual C++ Programmers 是一本由 Marcus Heege 编写的教程，专注于向 Visual C++ 开发人员介绍如何使用 C++/CLI 来开发 .NET 应用程序。这本书涵盖了 C++/CLI 的核心概念和技术，旨在帮助程序员充分利用 .NET Framework 的功能。" 本书主要知识点包括： 1. **C++/CLI 概述**：C++/CLI（以前称为 Managed Extensions for C++）是 Microsoft 推出的用于编写 .NET 应用程序的 C++ 扩展。它允许开发者使用 C++ 语法来创建托管代码，即运行在 .NET Framework 上的代码，同时也支持与非托管代码的交互。 2. **.NET Framework 知识**：学习 C++/CLI 必须理解 .NET Framework 的基础，包括 Common Language Runtime (CLR)、类型系统、垃圾回收机制、元数据以及 .NET 类库。 3. **托管与非托管代码的交互**：书中会详细讲解如何在 C++/CLI 项目中混合使用托管和非托管代码，以便利用现有的 C++ 代码库并将其与 .NET 平台集成。 4. **C++/CLI 语法**：介绍 C++/CLI 中特有的语法元素，如 `^` 用于引用管理的对象，以及 `cli::` 命名空间下的各种类型和操作。 5. **类和对象**：探讨如何在 C++/CLI 中创建和使用托管类，包括继承、封装和多态性等面向对象编程的概念。 6. **集合和泛型**：讲解如何使用 .NET 提供的集合类，以及如何利用泛型来创建类型安全的集合。 7. **异常处理**：C++/CLI 支持 .NET 异常处理模型，读者将学习如何捕获和处理 .NET 异常。 8. **资源管理**：深入理解 .NET 中的生命周期管理，包括智能指针（如 `gcroot`）和垃圾收集的工作原理。 9. **多线程编程**：介绍如何在 .NET 平台上进行多线程编程，以及如何使用 C++/CLI 实现并发和同步。 10. **Windows Forms 和 WPF**：可能会涵盖如何使用 C++/CLI 创建图形用户界面，包括 Windows Forms 和 Windows Presentation Foundation (WPF)。 11. **Interoperability with other .NET Languages**：学习如何与其他 .NET 语言（如 C# 或 VB.NET）的代码进行互操作。 12. **调试和性能优化**：讨论 C++/CLI 代码的调试技巧以及如何优化托管代码的性能。此书的作者 Marcus Heege 和技术审阅者 Stanley Lippman 的专业知识确保了内容的专业性和准确性，使得 Visual C++ 程序员能够顺利过渡到 .NET 开发环境，并充分利用 C++/CLI 的优势。书中的实例和实践指导将帮助读者掌握理论知识并应用到实际项目中。

What Is C++/CLI?

C++/CLI is a set of extensions made to the C++ language to benefit from the services that an

implementation of the CLI offers. These extensions are published as the ECMA-372 standard.

With the help of these extensions, a programmer can use .NET constructs in existing C++

code, as shown previously. Visual C++ 2005 implements the C++/CLI standard to support

executing code on the CLR.

Building C++/CLI Applications

To make the switch from C to C++, a new file extension was used. As you can see in the pre-

ceding HelloWorld3.cpp example, the file extension for C++/CLI applications remains

unchanged. However, there is still a need to distinguish between C++ compilation and

C++/CLI compilation—the result of native C++ compilation is native code, whereas the result

of C++/CLI compilation is managed code. If you try to compile the code on the command line,

as shown in the following, you’ll get compiler errors.

CL.EXE HelloWorld3.cpp

These errors will complain that System is neither a class nor a namespace name, and that the

identifier WriteLine is not found. Both the namespace System and the method WriteLine are

the managed aspects of your code. The Visual C++ compiler can act as a normal C++ compiler

or as a C++/CLI compiler. By default, it remains a native compiler. To use it as a C++/CLI com-

piler, you use the compiler switch /clr, as in the following command line:

CL.EXE /clr HelloWorld3.cpp

This simple HelloWorld3 application shows one of the advantages that C++/CLI has over all

other commonly used .NET languages: it provides source code compatibility with a good old

native language.

C++/CLI is a superset of the C++ language. A valid C++ program is also a valid C++/CLI

program. As a consequence, your existing code base is not lost. Instead of reimplementing

existing applications with a completely new language and programming infrastructure, you

can seamlessly extend existing code with .NET features.

The HelloWorld3.exe file created by the C++/CLI compiler and linker is a so-called .NET

assembly. For this chapter, it is sufficient to consider assemblies as the deployable units of the

.NET world. Chapter 4 will provide a more detailed definition of this term. The

HelloWorld3.exe assembly differs from assemblies created by other .NET languages because it

contains native code as well as managed code. An assembly like HelloWorld3.exe is also called

a mixed-code assembly.

A migration strategy based on C++/CLI can preserve huge investments in existing C++

source code. This is extremely important because there is a vast amount of C++ code that is

already written, tested, accepted, and in service. Furthermore, this strategy allows a partial

migration with small iterations. Instead of switching everything to .NET in one chunk, you can

flexibly use different .NET features when they seem appropriate.

CHAPTER 1 ■ WHY C++/CLI? 3

// HelloWorld4.cpp

// compile with "cl /MD HelloWorld4.cpp /link ManagedCode.obj UnmanagedCode.obj"

#include <stdio.h>

extern void fManaged(); // implemented in ManagedCode.cpp

int main()

{

printf("Hi from native code.\n");

fManaged();

}

If you use the command shown in the comment of this code, the C++/CLI compiler will

generate a native object file, HelloWorld4.obj, and link it together with ManagedCode.obj and

UnmanagedCode.obj into the application HelloWorld4.exe. Since HelloWorld4.obj is a native

object file, HelloWorld4.exe has a native entry point. The printf call in main is a native call

from a native function. This call is done without a switch between managed and unmanaged

code. After calling printf, the managed function fManaged is called. When an unmanaged

function like main calls a managed function like fManaged, an unmanaged-to-managed transi-

tion takes place. When fManaged executes, it uses the managed Console class to do its output,

and then it calls the native function fNative. In this case, a managed-to-unmanaged transition

occurs.

The HelloWorld4 application was written to explain both kinds of transitions. It is

extremely helpful to have both these options and to control in a very fine-grained way when

a transition from managed code to unmanaged code, or from unmanaged code to managed

code, takes place. In real-world applications, it is important to avoid these transitions,

because method calls with these transitions are slower. Reducing these transitions is key to

avoiding performance penalties in C++/CLI. To detect performance problems, it can be very

important to identify transitions between managed and unmanaged code. Reducing perform-

ance penalties is often done by introducing new functions that replace a high number of

managed/unmanaged transitions with just one. Chapter 9 gives you detailed information

about internals of managed/unmanaged transitions.

The code samples used so far have used the simplest possible method signature. How-

ever, the interoperability features of C++/CLI allow you to use any native type in code that is

compiled to managed code. This implies that methods called via managed/unmanaged tran-

sitions can use any kind of native type. Chapter 8 will discuss all details of type transitions.

DLLs with Managed Entry Points

You can also factor managed code out into a separate DLL so that your existing projects

remain completely unmanaged. Figure 1-4 shows a simple example of such a scenario.

CHAPTER 1 ■ WHY C++/CLI? 7

剩余335页未读，继续阅读

pyimt

粉丝: 0
资源: 1

精通C++/CLI：Visual C++程序员的.NET指南

Expert C++/CLI

Programming with Microsoft Visual C++ .NET

Expert C++ / CLI .NET for Visual C++ Programmers (带完整目录)

C++/CLI入门指南：.NET for Visual C++

精通Visual C++/CLI：.NET编程指南

精通C++/CLI：面向Visual C++程序员的.NET指南

精通C++/CLI .NET：面向Visual C++程序员的指南

C++/CLI深度探索：.NET与Visual C++的完美结合

Visual C++程序员的C++/CLI与.NET专家指南

《Expert C++/CLI for Visual C++ Programmers》核心编程指南

最新资源