One of the best ways to understand how the CLR works internally is to have a look at the SSCLI [a.k.a Rotor] source code. In How the SSCLI [a.k.a. Rotor] managed "new" works, I have used Rotor source code to discuss what happens behind the scenes when you use the managed new operator to instantiate a managed type, discussing implications of object size, how requests from multiple threads are handled, the different validations that are done, when out-of-memory exception is thrown, etc. If you are ......
One of the best ways to understand how the CLR works internally is to have a look at the SSCLI [a.k.a Rotor] source code. In How the SSCLI [a.k.a. Rotor] managed "new" works, I have used Rotor source code to discuss what happens behind the scenes when you use the managed new operator to instantiate a managed type, discussing implications of object size, how requests from multiple threads are handled, the different validations that are done, when out-of-memory exception is thrown, etc. If you are ......
[Original Post Date: 5th September 2005] Share Source CLI, better known as Rotor, is one of the best ways to understand how .NET Framework works. And with the source code availability as part of Rotor distribution, its an excellent academic/hobby interest - you can extend it by adding more functionality, or modify the existing one and see how it behaves. Yesterday, I went about doing the same. One of the functionality which I found missing in Rotor is that of enumerating system process list. .NET ......
Just finished extending Rotor's ThreadPool class to support SetMaxThreads and SetMinThreads methods - to modify the extent of the threadpool maintained by the Rotor runtime - just like .NET FX 2.0 has it. Will post the source code soon...meanwhile, here's my implementation of SetMinThreadsInternal in Win32ThreadPool.cpp: /**************************... // Will be used to set the minimum number of threads in the Rotor Threadpool // Kumar Gaurav Khanna - 22-Jul-2004 ......