Geeks With Blogs

News
WinToolZone - Spelunking Microsoft Technologies
I work as a developer on the Common Language Runtime (CLR) team, specifically in the areas of exception handling and CLR hosting.
Disclaimer

The information in this weblog is provided "AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion. Inappropriate comments will be deleted at the authors discretion. All code samples are provided "AS IS" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Inside and Out... An attempt to understand technology better... Rotor
How the SSCLI [a.k.a. Rotor] managed "new" works
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 ......

Posted On Thursday, March 29, 2007 1:46 PM

How the SSCLI [a.k.a. Rotor] managed "new" works
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 ......

Posted On Tuesday, February 13, 2007 2:48 AM

Adding process enumeration support in Rotor v1.0
[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 ......

Posted On Thursday, January 5, 2006 9:44 AM

..and ThreadPool.GetMinThreads
And I am finally done with extending the Rotor's ThreadPool class. Finished implementing the GetMinThreads method.

Download the source code from http://www.wintoolzone.com/showpage.aspx?url=rotor.aspx.

Posted On Sunday, July 25, 2004 2:46 PM

Rotor - SetMaxThreads, SetMinThreads
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 ......

Posted On Thursday, July 22, 2004 7:02 PM

Copyright © Gaurav Khanna | Powered by: GeeksWithBlogs.net