"CLR Inside Out" Needs Your Ideas

One of the benefits that we at MSDN Magazine are proud to be able to offer readers is access to many of the actual product groups at Microsoft.  For those of you who read the magazine, you know that we run a column called CLR Inside Out - the column is authored by the product team that develops and maintains the .NET CLR/DLR and its goals are to provide you with an "under the covers" view of the runtime and to provide insight into some of the thinking that went into its creation.

Particularly with this column, we want to make sure that we are providing you not only deep insight - but relevant deep insight.  And as a result, the CLR team wants to know what you are interested in reading about as we move into 2008.


Comments (5)

  1. Vibhu says:


    Sure we will like to read the colum in 2008 and beyond that. It is the Resource to understand the real concept

    overall, otherwise there is always too much hue and cry for a thing making it difficult to understand.

  2. TraumaPony says:

    I’d love to see how the JITter optimizes code.

  3. Since the tolerance for problems is probably much lower in a library/framework, I would be most interested in your exception/error handling decisions.

    99% of books totally ignore error/exception handling (to concentrate on the main point of the book) I would speculate that exception handling is not done uniformly well in the "real" world.

    How about covering:

    – how you pass "errors" (is it ALWAYS exceptions – or are there a few cases where you use return values or some other method)

    – how you decided which exceptions are caught, which are not, etc

    – how you decide on the level of "robustness" – are some parts of the framework better than others? especially in the face of very unusual exceptions?

  4. Sam says:


    I would like to see articles on memory management, multithreading, 64-bit vs. 32-bit CLR, security, deployment issues, performance benchmarks…

    Keep up the good work. CLR Inside Out is my favorite read in MSDNMag.

    Thank you


Skip to main content