Everyone has probably dealt with an annoying performance issue at some point or the other. Performance optimization is a hard problem and we could sure use some help from you. We have a survey posted at the CLR and Framework Performance blog over here.
And the videos keep coming in!
We have Shawn Farkas who works on the security model, talking about the new managed security model. Check out the video here.
And then we have Surupa Biswas, from the CLR Code Generation team, talking about the new Targeted Patching work in CLR 4.
Surupa Biswas has a post in the CodeGen team blog on new features in NGen coming out as part of CLR 4. The post covers NGen SxS (that’s side-by-side) and multi-proc NGen, and goes into detail on the work that went into making Targeted Patching possible.
We have more Channel 9 videos from the CLR team for your enjoyment!
The Base Class Libraries (BCL) team talks about some of the new features in the next version of BCL over here.
We have Maoni Stephens and Andrew Pardoe talking about Background Garbage Collection over here.
A couple of weeks back my PM and I did a channel9 video on Background GC. Take a look:
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.
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.
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”
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 different (spin up a new AppDomain).
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,