I think CLR Profiling API is one of the coolest things in CLR. Here is a nice article I just found on msdn about Whidbey Profiling APIs. Note that Everett Profiling API and Whidbey Profiling API are completely not compatible. You have to explicitly implement...

I was reading Joel's blog about new stuff in Reflection and he mentioned ReflectionOnly context. Apart from the Generics, token handle resolutions, LCG, ReflectionOnly context (actually a loader feature) had a big impact in Reflection area in Whidbey...

I've got several inquiry emails about this issue, so I think it is a good idea to publish the problem here. Say we have: public class Test { public void Teste<U>(U teste, int i) { Console.WriteLine(teste); } public void Teste<U>...

Our Reflection QA definitely knows a lot and he is now having a blog of his own: http://blogs.msdn.com/haibo_luo A little advertisement, I know he is going to have something cool coming up soon. Just keep an eye on it.

Users are not supposed to operate on same Reflection.Emit object on multiple threads. Reflection.Emit Objects are *NOT* thread-safe. It is certainly OK to operate on different Reflection.Emit objects on different threads. We have been discovering issues...