What is the relationship between domains, threads, stack and managed heap?

Question

.NET

Hello everyone
After reading Richter, there are a lot of contradictions and misunderstandings:
If an application is launched into a process - the required version of the CLR is initialized for it (or two at once) - in the CLR there is a logical splitting of the code and the managed heap into domains, as well as classes that use winApi threads and are they an abstraction - threads that can execute different code from different domains and have a 1 mb stack - the same one for storing local variables, method arguments, value types and a reference to the managed heap? Or is it the wrong stack?
There is also a thread kernel that stores the values ​​of the processor registers, and loads it for execution with a context switch.
The picture is quite abstract, can you describe it all more concisely or advise something to read?

Answer 1

Found something
msdn.microsoft.com/ru-ru/magazine/cc163791(en-us).aspx