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

4星 · 超过85%的资源需积分: 14 106 浏览量更新于2024-07-18 1 收藏 2.49MB PDF 举报

"Expert C++ / CLI .NET for Visual C++ Programmers" 是一本由 Marcus Heege 编写的书籍，旨在帮助经验丰富的 C++ 开发者理解和掌握 C++/CLI，这是一种用于 .NET 平台的编程语言，能够利用 .NET Framework 的特性。本书详细介绍了如何将 C++ 与 .NET 功能相结合，实现混合编程，同时保持源代码的高兼容性。在 C++/CLI 中，它构建于 C++ 之上，提供了与 C++ 源代码高度兼容的特性。这意味着开发者可以在使用 C++/CLI 编译器的情况下编写类似以下的代码，这些代码在 C++ 中也是合法的。这种兼容性使得已有的 C++ 项目可以更平滑地过渡到 .NET 平台，同时利用 .NET 提供的服务，如垃圾回收、类型安全和面向服务的架构。 C++/CLI 的核心目标是提供一个桥梁，连接传统的 C++ 世界与 Microsoft 的 .NET Framework。它允许开发者使用托管代码（managed code）和非托管代码（unmanaged code）的混合编程模式，这对于那些需要调用 C++ 库或者需要高性能计算的 .NET 应用程序特别有用。C++/CLI 提供了诸如引用类型（reference types）、接口（interfaces）以及对 .NET 集合和事件等概念的支持。书中的内容可能包括以下几个方面： 1. **C++/CLI 基础**：介绍 C++/CLI 的基本语法和概念，如托管类（managed classes）、句柄（handles）、引用类型和值类型的区别，以及如何声明和使用托管数组。 2. **.NET Framework 交互**：讲解如何调用 .NET 类库，使用 .NET 集合，以及集成 .NET 事件处理机制。 3. **互操作性**：讨论如何在 C++/CLI 中使用 PInvoke（Platform Invoke）来调用非托管的 DLL，以及如何使用 C++/CLI 进行 COM 互操作。 4. **内存管理和生命周期**：解释 .NET 的垃圾回收机制以及如何在 C++/CLI 中管理对象的生命周期。 5. **高级主题**：涵盖模板（templates）、异常处理（exception handling）、多线程（multithreading）和并发编程（concurrency）在 C++/CLI 中的应用。 6. **实例分析**：通过实际的项目或代码示例，展示如何在实践中结合 C++ 和 .NET 技术。 7. **最佳实践**：给出使用 C++/CLI 进行开发时的建议和技巧，帮助开发者避免常见的陷阱和问题。这本书的作者 Marcus Heege 和技术审查者 Stanley Lippman 都是 C++ 领域的专家，他们共同确保了内容的专业性和准确性。此外，这本书还包括了一个编辑团队和专业审稿人的支持，确保了内容的质量和深度。 "Expert C++ / CLI .NET for Visual C++ Programmers" 是一本为希望在 .NET 平台上利用 C++ 优势的开发者准备的指南，涵盖了从基础到高级的各种主题，旨在帮助读者熟练掌握 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页未读，继续阅读

亱

粉丝: 10
资源: 7

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

Expert C++ Programming epub

Expert C++/CLI

Expert C++ Programming 2018年英文版

Expert C++/CLI: .NET for Visual C++ Programmers

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

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

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

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

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

C++/CLI专家指南：Visual C++程序员的.NET实战

最新资源