《App研发录:架构设计、Crash分析和竞品技术分析》迷你书.pdf
《App研发录:架构设计、Crash分析和竞品技术分析》迷你书.pdf
The .NET Framework consists of two parts: the common language runtime (CLR) and the Framework Class Library (FCL). The CLR provides the programming model that all application types will use. The CLR includes its own file loader, memory manager (the garbage collector), security system (code access security), thread pool, and so on. In addition, the CLR offers an object-oriented programming model that defines what types and objects are and how they behave. The Framework Class Library provides an object-oriented API set that all application models will use. It includes type definitions that allow developers to perform file and network I/O, scheduling tasks on other threads, drawing shapes, comparing strings, and so on. Of course, all of these type definitions follow the programming model set forth by the CLR.
This document is a distillation and a simplication of the most basic guide- lines described in detail in a book titled Framework Design Guidelines by Krzysztof Cwalina and Brad Abrams. Framework Design Guidelines were created in the early days of .NET Frame- work development. They started as a small set of naming and design con- ventions but have been enhanced, scrutinized, and rened to a point where they are generally considered the canonical way to design frameworks at Mi- crosoft. They carry the experience and cumulative wisdom of thousands of developer hours over several versions of the .NET Framework.