This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
Initial commit of 'Introduction to the CLR' #115
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jkotas
added a commit
that referenced
this pull request
Feb 6, 2015
Initial commit of 'Introduction to the CLR'
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This document describes the .NET CLR architecture and the motivation behind fundamental characteristics of the product. It is arguably the best description of the CLR (given the degree of insight), from one of the key founding (and current) CLR architects, Vance Morrison / @vancem.
This document is the first of the "Book of the runtime" chapters. It is also (quite appropriately) the first that we are releasing. These documents were written 5-10 years ago. Some of them, like this one, are just as relevant now as when they were written. Other documents have become obsolete since they describe features and design decisions that are no longer present in the product. We'll release the ones that remain meaningful.
Each of the BoTR documents, including this one, were written with a certain perspective. We did not think it was right to mutate the document to make it more "2015". They remain the docs that they were, modulo a few spelling corrections and a conversion to markdown.