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

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

"Expert C++/CLI - .NET for Visual C++ Programmers by Marcus Heege" 本书《Expert C++/CLI》是针对C++/CLI编程语言的一本专业指南，作者Marcus Heege深入浅出地介绍了如何使用C++/CLI进行.NET框架的开发。这本书适合已经熟悉C++的开发者，尤其是那些希望将他们的技能扩展到Microsoft的.NET环境中的开发者。C++/CLI是C++的一个扩展，它允许程序员充分利用.NET Framework的功能，如托管代码、通用类型系统和组件交互。 C++/CLI（之前称为Managed Extensions for C++）是微软推出的一种语言，它提供了与.NET Framework的紧密集成，同时保留了C++的语法和特性。通过C++/CLI，开发者可以直接创建和操作.NET对象，使用.NET的特性，如接口、属性、事件和泛型，同时还能利用C++的底层控制能力。书中可能涵盖了以下关键知识点： 1. **C++/CLI基础**：介绍C++/CLI的关键语法元素，如`cli::`命名空间、`^`引用类型（handle-to-object）、`%`值类型（handle-to-value）以及`__gc`关键字（在较旧的文献中表示对象管理）。 2. **.NET Framework概念**：讲解.NET Framework的基本结构，包括类库、元数据、Common Language Runtime (CLR)以及垃圾回收机制。 3. **托管与非托管代码交互**：阐述如何在C++/CLI中混合使用托管和非托管代码，以利用现有C++库或在.NET环境中访问原生API。 4. **类型转换**：讨论如何在.NET类型和C++/CLI类型之间进行转换，包括装箱和拆箱操作。 5. **资源管理**：解释智能指针（例如`gcroot`）和自动垃圾回收如何简化资源管理，以及何时需要手动释放非托管资源。 6. **泛型和模板**：比较C++模板与.NET泛型，展示如何在C++/CLI中使用泛型类和方法。 7. **异常处理**：介绍.NET和C++的异常模型，以及如何在C++/CLI中进行兼容性处理。 8. **组件编程**：讨论如何创建和使用.NET组件，包括接口实现、属性、事件和设计模式。 9. **Windows Forms和WPF**：如果涉及UI开发，可能会介绍如何用C++/CLI构建Windows Forms或Windows Presentation Foundation (WPF)应用程序。 10. **调试和性能优化**：分享C++/CLI应用程序的调试技巧，以及如何对.NET应用进行性能分析和优化。技术审稿人Stanley Lippman的参与增加了本书的专业性，他是C++社区的知名人物，曾与Bjarne Stroustrup共同编写过经典著作《C++ Primer》。总体而言，《Expert C++/CLI》旨在帮助开发者快速掌握C++/CLI语言，从而更好地利用.NET Framework进行高效、可靠的软件开发。通过阅读此书，读者可以提升在C++和.NET结合的开发环境中的技能，无论是开发新项目还是维护既有代码库，都将受益匪浅。

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页未读，继续阅读

u010723677

粉丝: 0
资源: 7

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

Expert C++/CLI Source Code

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

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

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

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

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

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

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

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

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

最新资源