C#代码的编译与执行过程(摘自ms inside c#)
来源:互联网 发布:知乎精华话题 编辑:程序博客网 时间:2024/05/23 02:00
<script type="text/javascript"><!--google_ad_client = "pub-2947489232296736";/* 728x15, 创建于 08-4-23MSDN */google_ad_slot = "3624277373";google_ad_width = 728;google_ad_height = 15;//--></script><script type="text/javascript"src="http://pagead2.googlesyndication.com/pagead/show_ads.js"></script>
2.You then compile it using the C# compiler (csc.exe) into an EXE.
3.The C# compiler outputs the msIL code and a manifest into a read-only part of the EXE that has a standard PE (Win32-portable executable) header.
So far, so good. However, here's the important part: when the compiler creates the output, it also imports a function named _ CorExeMain from the .NET runtime.
4.When the application is executed, the operating system loads the PE, as well as any dependent dynamic-link libraries (DLLs), such as the one that exports the _ CorExeMain function (mscoree.dll), just as it does with any valid PE.
5.The operating system loader then jumps to the entry point inside the PE, which is put there by the C# compiler. Once again, this is exactly how any other PE is executed in Windows.
However, since the operating system obviously can't execute the msIL code, the entry point is just a small stub that jumps to the _ CorExeMain function in mscoree.dll.
6.The _ CorExeMain function starts the execution of the msIL code that was placed in the PE.
7.Since msIL code cannot be executed directly—because it's not in a machine-executable format—the CLR compiles the msIL by using a just-in-time (JIT) compiler (or JITter) into native CPU instructions as it processes the msIL. JIT compiling occurs only as methods in the program are called. The compiled executable code is cached on the machine and is recompiled only if there's some change to the source c
代码的编译与执行过程(摘自ms inside c#)';return true">
<script type="text/javascript"><!--google_ad_client = "pub-2947489232296736";/* 728x15, 创建于 08-4-23MSDN */google_ad_slot = "3624277373";google_ad_width = 728;google_ad_height = 15;//--></script><script type="text/javascript"src="http://pagead2.googlesyndication.com/pagead/show_ads.js"></script>
<script type="text/javascript"><!--google_ad_client = "pub-2947489232296736";/* 160x600, 创建于 08-4-23MSDN */google_ad_slot = "4367022601";google_ad_width = 160;google_ad_height = 600;//--></script><script type="text/javascript"src="http://pagead2.googlesyndication.com/pagead/show_ads.js"></script>
1.You write source code in C#. 2.You then compile it using the C# compiler (csc.exe) into an EXE.
3.The C# compiler outputs the msIL code and a manifest into a read-only part of the EXE that has a standard PE (Win32-portable executable) header.
So far, so good. However, here's the important part: when the compiler creates the output, it also imports a function named _ CorExeMain from the .NET runtime.
4.When the application is executed, the operating system loads the PE, as well as any dependent dynamic-link libraries (DLLs), such as the one that exports the _ CorExeMain function (mscoree.dll), just as it does with any valid PE.
5.The operating system loader then jumps to the entry point inside the PE, which is put there by the C# compiler. Once again, this is exactly how any other PE is executed in Windows.
However, since the operating system obviously can't execute the msIL code, the entry point is just a small stub that jumps to the _ CorExeMain function in mscoree.dll.
6.The _ CorExeMain function starts the execution of the msIL code that was placed in the PE.
7.Since msIL code cannot be executed directly—because it's not in a machine-executable format—the CLR compiles the msIL by using a just-in-time (JIT) compiler (or JITter) into native CPU instructions as it processes the msIL. JIT compiling occurs only as methods in the program are called. The compiled executable code is cached on the machine and is recompiled only if there's some change to the source c
<script type="text/javascript"><!--google_ad_client = "pub-2947489232296736";/* 728x15, 创建于 08-4-23MSDN */google_ad_slot = "3624277373";google_ad_width = 728;google_ad_height = 15;//--></script><script type="text/javascript"src="http://pagead2.googlesyndication.com/pagead/show_ads.js"></script>
<script type="text/javascript"><!--google_ad_client = "pub-2947489232296736";/* 160x600, 创建于 08-4-23MSDN */google_ad_slot = "4367022601";google_ad_width = 160;google_ad_height = 600;//--></script><script type="text/javascript"src="http://pagead2.googlesyndication.com/pagead/show_ads.js"></script>
- C#代码的编译与执行过程(摘自ms inside c#)
- C#代码的编译与执行过程(摘自ms inside c#)
- 代码的编译连接与执行过程
- C编译执行的过程
- 代码的编译、连接与执行过程分析
- C文件如何成为可执行文件(编译、链接、执行)——摘自《程序员的自我修养》
- C语言学习笔记(三)C的程序结构与编译执行过程
- C#代码的编译过程
- java代码的编译和执行过程
- C#代码编译过程
- c#代码编译过程
- C程序编译执行过程(转载)
- java代码编译、执行过程
- 反编译C程序为汇编代码,汇编代码执行过程的分析与思考
- c代码编译过程
- C程序编译执行过程
- C 程序编译执行过程
- C程序编译执行过程
- PHP/MySQL三日通-第一天(二)
- c#里正则表达式的例子
- PHP/MySQL三日通-第二天(一)
- 使用 sqlserver来存放和取得 session
- PHP/MySQL三日通-第一天(一)
- C#代码的编译与执行过程(摘自ms inside c#)
- PHP5 OOP编程之代理与定制异常
- 三、ASPNET中实现在线用户检测(使用后台守护线程)
- 大型系统上PHP令人不爽的九大原因
- session 和 viewstate 的比较
- 通过缓存数据库结果提高PHP性能
- 在ASP.NET中使用Session与Application 对象(续)
- 编程设计:PHP 5中多态性的实现方案浅析
- Passport 你的网站(在你的WebSite上实现MS Passport )上