A couple of weeks back my PM and I did a channel9 video on Background GC. Take a look: https://channel9.msdn.com/shows/Going+Deep/Maoni-Stephens-and-Andrew-Pardoe-CLR-4-Inside-Background-GC/
Now that .Net 4 Beta1 is out, you'll see a number of posts on this blog covering new CLR features in CLR 4. Grant Richins, a developer on our team, wrote a post on tail call improvements in CLR 4 at the CLR Code Generation blog. The post deals with JIT ETW Tracing in .Net 4 and specifically covers new ETW events exposed by the JIT. Prior ...
Vance Morrison, a CLR architect, recently gave an interview to Channel 9 where he walks through the history of the CLR (he's been on our team since it's very beginning), the upcoming version, his favorite features in CLR v4, and what the future looks like. He also talks about concurrency (and the role that CLR plays), aspects of...
The Dynamic Language Runtime allows you to implement a dynamic language (such as Ruby or Python) on top of the CLR. There are a lot of challenges to making everything work right. One particularly difficult aspect was enabling Ruby to attach arbitrary "properties" to instanced .NET managed objects at runtime. If a Ruby developer sets an instance var...
This is the first in a series of posts where we discuss the reasoning behind “obsoleting” specific APIs. If you use AppDomain.AppendPrivatePath, or look at MSDN, you’ll notice it’s obsolete. This frustrates people because the alternative suggested (AppDomainSetup.PrivateBinPath) requires you to do something entirely d...
Managed exception handling is built on Windows OS’s Structured Exception Handling, commonly referred to as SEH (to learn more about SEH, please read Matt Pietrek’s excellent article first). This implies that CLR understands how to interoperate between SEH and managed exception systems, which is a very key point since SEH is based upon the notion of...
Managed exception handling is built on Windows OS’s Structured Exception Handling, commonly referred to as SEH (to learn more about SEH, please read Matt Pietrek’s excellent article first). This implies that CLR understands how to interoperate between SEH and managed exception systems, which is a very key point since SEH is based upon the notion of...
The May installment of the “CLR Inside Out” column in MSDN magazine is now available on line. This month we have an article from Aarthi Ramamurthy and Mark Miller on Understanding The CLR Binder. It covers some best practices for assembly binding and loading using the CLR. You can find a list of all “CLR Inside ...
Eric Eilebrecht, a developer on our team, has just started a multi-part series on TheadPool improvements in the upcoming CLR v4.0. The first post is pretty fascinating and begins with a brief introduction on thread pools and it's design. The post deals with changes in thread pool's design, due to increasing core counts today. In the ...
System.Threading.ThreadAbortException is just plain weird. For instance, most exceptions happen because of something code did on its own thread: even asynchronous exceptions are caused by something your code did on the current thread. (Note for the nitpickers: gamma rays can cause a bit in memory to flip randomly, bringing about unexpected pr...
