Compiling MSIL to native code.
将MSIL编译为本机代码。
The compiler creates an file that contain MSIL.
编译器将创建一个包含MSIL的文件。
Demonstrates the use of reflection in a pure MSIL application.
演示如何在纯m SIL应用程序中使用反射。
The compiler found a (probable) DLL entry point compiled to MSIL.
编译器找到编译为MSIL的(可能)DLL入口点。
Gets the value of the specified local variable in this MSIL stack frame.
取得这个框架中，区域变数的列举值。
Displays the total MSIL bytes JIT-compiled since the application started.
显示自应用程序启动后实时编译的总MSIL字节数。
To implement generics, the CLR and the MSIL language undergo some changes.
为了编写范型，CLR以及MSIL语言经历了一些修改。
The optimizations done on MSIL code are a large subset of those done on unmanaged code.
对MSIL代码的优化是对非托管代码进行优化的一个大子集。
At execution time, a just-in-time (JIT) compiler translates the MSIL into native code.
在执行时，实时(JIT)编译器将MSIL翻译为本机代码。
You can run the resulting executable to determine whether the MSIL performs as expected.
可以运行生成的可执行文件以确定 MSIL是否按预期执行。
There are no MSIL instructions that can be used to access the Constant table at run time.
没有MSIL指令，可用于在执行阶段存取常数资料表。
When you compile a generic class, MSIL contains placeholders for each parameterized type.
当你编译一个范型类时，MSIL为每一个参数化的类型预留了空间。
Explains how to create executable code by emitting MSIL instructions into properties and methods.
说明如何借由将MSIL指令发出到属性和方法中，以建立可执行的程序码。
Furthermore, the generated MSIL and associated native code can be reclaimed when no longer needed.
此外，不再需要产生的MSIL和关联的机器码时，也可以将它们回收。
Mixed assemblies are capable of containing both unmanaged machine instructions and MSIL instructions.
混合程序集能够同时包含非托管计算机指令和MSIL 指令。
The JIT reads in the MSIL and begins to perform optimizations that are very sensitive to changes in the MSIL.
JIT读取MSIL并开始执行优化，这些优化对MSIL中的变化很敏感。
Each row of each metadata table is uniquely identified in the MSIL portion of the PE file by a metadata token.
元数据标记在PE文件的MSIL部分中唯一确定每个元数据表的每一行。
Metadata tokens are conceptually similar to Pointers, persisted in MSIL, that reference a particular metadata table.
元数据标记在概念上和指针相似，永久驻留在MSIL中，引用特定的元数据表。
It performs the conversion from MSIL to native code before running the application instead of while the application is running.
它在应用程序运行之前而不是在应用程序运行过程中执行从MSIL到本机代码的转换。
How the MSIL for a generic type is used differs based on whether the supplied type parameter is a value type or reference type.
泛型类型的MSIL的使用因所提供的类型参数是值类型还是引用类型而不同。
The JIT compiler continues to process MSIL at the new address until it encounters another metadata token and the process is repeated.
JIT编译器继续在新地址处理MSIL，直到它遇到另一个元数据标记，之后，重复该过程。
One instruction sequence of MSIL might be very amenable to optimization, whereas another (semantically equivalent) sequence stifles optimization.
一个MSIL指令序列也许能够很好地进行优化，但另一个(语义上等同的)序列却可能抑制优化。
The resulting source code then passes through the rest of the standard compiler phases producing MSIL byte-code with IKVM library references.
接下来，生成的源代码再经过其他标准的编译器编译并使用IKVM库引用来生成MSIL字节码。
The runtime updates its metadata tables, places the new MSIL into the process, and sets up a just-in-time (JIT) compilation of the new MSIL.
运行时将更新其元数据表、将新MSIL置于进程中并设置对新MSIL的实时(JIT)编译。
Of course, you also need to consider the performance cost associated with Y.cpp being MSIL, and ensure that this is the right tradeoff for the application.
当然，您也需要考虑从Y.c pp生成msil的相关性能代价，并确保这种折衷对应用程序有利。
During this compilation, code must pass a verification process that examines the MSIL and metadata to find out whether the code can be determined to be type safe.
在此编译过程中，代码必须通过验证过程，该过程检查MSIL和元数据以查看是否可以将代码确定为类型安全。
Because of potential problems with loading a DLL whose entry point has been compiled to MSIL, you are strongly discouraged from compiling a DLL entry point function to MSIL.
由于加载入口点已编译为MSIL的DLL时存在一些潜在问题，因此强烈建议不要将DLL入口点函数编译为MSIL。
Whether the code generated by the Visual C++ compiler is MSIL or unmanaged code, the optimizer that generates the code is the same one that has been developed and tuned for over a decade.
不管Visual C++编译器生成的代码是MSIL还是非托管代码，生成代码的优化器还是十几年前就已开发并已进行调整的优化器。
One main difference is that Phoenix groups all the Microsoft compilers (more than 25 of them) into one, generating the binaries or MSIL code for all the languages and platforms Microsoft supports.
一个主要的区别是，Phoenix将微软所有的编译器(超过25个)聚集成一个，为微软支持的所有语言和平台生成二进制文件或MSIL代码。
One main difference is that Phoenix groups all the Microsoft compilers (more than 25 of them) into one, generating the binaries or MSIL code for all the languages and platforms Microsoft supports.
一个主要的区别是，Phoenix将微软所有的编译器(超过25个)聚集成一个，为微软支持的所有语言和平台生成二进制文件或MSIL代码。
应用推荐