什么＆QUOT; EE＆QUOT;指SOS？ [英] What the "EE" means in SOS?

问题描述

我找到了EE是一个神奇的词对我来说。

I found "EE" is a magic word for me.

内的CLR，有一个EEClass，这是由CLR类加载器创建的。我不知道为什么它被称为EEClass。

Inside CLR, there is a "EEClass", which is created by CLR class loader. And I don't know why it is called EEClass.

现在，来到SOS世界，有更多EE这里，像 EEHeap，EEStack [-EE]，Name2EE .... 难道他们站在这里同一个意思？

Now, come to the SOS world, there are more EE here, like EEHeap, EEStack [-EE], Name2EE.... Do they stand for the same meaning here ?

推荐答案

在CLR开始长寿命，然后才通过运行.NET code。开始为通用运行系统项目42，失败，但其部分在后续项目中幸存下来，像.NET中highfaluting项目。一直持续到NGWS（下一代Windows服务），然后就演变为执行引擎.NET。 42是该集团在微软总部工作的建设数量。

The CLR started life long before it was adopted to run .NET code. Started as the Universal Runtime in Project 42, a highfaluting project that failed but whose parts survived in subsequent projects, like .NET. Continued into NGWS (Next Generation Windows Services) before it evolved as the execution engine for .NET. 42 was the building number that the group worked in on the Microsoft campus.

若干缩写活了下来，在SSCLI20源$ C ​​$ c和名字，你看到后面的调试器和头文件非常明显。他们的一知半解：

Several acronyms survived, quite visible in the SSCLI20 source code and names you see back in the debugger and header files. A smattering of them:

• 城市轨道交通，通用运行。古代，它只是保留在本机错误codeS从管理code得到的，他们有工厂code 19，FACILITY_URT的WinError.h中头文件研究。这使得任何这样的错误code值0x8013xxxx。

• URT, Universal Runtime. Ancient, it just remains in the native error codes you get from managed code, they have facility code 19, FACILITY_URT in the WinError.h header file. Which makes any such error code value 0x8013xxxx.

COM +或COMPLUS。同样古老的，COM +是COM的发展，值得注意的是失去了中间件战争Java和组在Microsoft的具有小学项目42责任的名称。仍可以看到异常的名称，其中包括原生异常$ C $下任何的.NET异常：0xe0434f4d。 434f4d是ASCII codeS为COM。在CLR本身实际使用很少的COM code，只是为了生产从PDB和定制托管，调试器和分析器接口堆栈跟踪。

COM+ or COMPlus. Also ancient, COM+ was the evolution of COM, notable for losing the middle-ware war to Java and the name of the group in Microsoft that had primary Project 42 responsibility. Still visible in the names of exceptions, including the native exception code for any .NET exception: 0xe0434f4d. 434f4d are the ASCII codes for "COM". The CLR itself actually uses very little COM code, just to produce the stack trace from the pdb and the custom hosting, debugger and profiler interfaces.

COR，公共对象运行。这开始后，项目42位出现的首字母缩写。生存在SDK头文件中的所有的名字，像Cor.h，CorError.h，CorDebug.h和多个托管API名称一样CorBindToRuntimeEx的。在.NET 4的版本顺便说一句重命名为CLR。

COR, Common Object Runtime. The acronym that starts appearing after the Project 42 bits. Survives in all the names of the SDK header files, like Cor.h, CorError.h, CorDebug.h and several hosting api names, like CorBindToRuntimeEx. Renamed to "CLR" in the .NET 4 versions btw.

EE，执行引擎。出现在CLR的部分被认为特别适合于运行.NET code的名字。当你发现了。

EE, Execution Engine. Appears in the names of parts of the CLR that were adapted specifically for running .NET code. As you found out.

SOS，罢工的儿子。使用的DAC（数据访问组件）挂接到并揭示内部CLR数据结构的调试器扩展。罢工是用来获取.NET 1.0版去，回来的时候它有内部的项目名称闪电调试器扩展名。雷击，你得到它。演变成一般的调试工具，从而成为打击的儿子。当您尝试加载与不同的CLR版本中创建一个小型转储DAC是从mscordacwks.dll运行时支持DLL，你会得到错误信息可见。

SOS, Son of Strike. A debugger extension that uses the DAC (Data Access Component) to hook into and reveal internal CLR data structures. Strike was the name of a debugger extension used to get .NET version 1.0 going, back when it had the internal project name Lightning. Lighting Strike, you get it. Evolved as a general debugging tool, thus becoming the son of Strike. DAC is visible from the mscordacwks.dll runtime support DLL and the error message you get when you try to load a minidump that was created with a different CLR revision.

内部项目名称也是.NET Framework的源$ C ​​$ C醒目可见。 .NET 1.0是闪电，.NET 1.1是埃弗里特，.NET 2.0是Whidbey的，WPF是阿瓦隆，WCF是靛蓝。

The internal project names are also prominently visible in .NET Framework source code. .NET 1.0 was Lightning, .NET 1.1 was Everett, .NET 2.0 was Whidbey, WPF was Avalon, WCF was Indigo.

有一个类似的那种涉及CLR正在发生，现在highfaluting项目。超级秘密，其code的名字叫绿。很少有人知道它，除了它的目的是实现基于管理code整个操作系统。对否则也发表奇异原型的后续。

A similar kind of highfaluting project that involves the CLR is taking place right now. Super-secret, its code name is Midori. Little is known about it, other than it aims to implement an entire operating system based on managed code. A follow-up on the otherwise well published Singularity prototype.

这篇关于什么＆QUOT; EE＆QUOT;指SOS？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！