After being in Exchange for almost a year, I tend to forget the how to run Reflection.Emit that I was once so familiared with. Occasionally, I would receive emails from this blog asking how to emit this, how to emit that. Before, the solutions came directly...

I am going to program in the Server world using managed code! Maybe after some time, I will start a new blog for IT professionals about Clustering in Exchange. But currently this blog is not likely to have new contents about the most updated CLR technology...

ProfilerCallback.cpp // This is the function that will invoke the managed code through COM interop on another thread // this function creates the CCW object // [in] this pointer DWORD WINAPI CreateManagedStub(LPVOID lpParam) { _ManagedStub *...

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...

We have found some limitations in Reflection.Emit that you cannot emit types that can be compiled in C# compiler. You are unlikely to hit it in daily emit job but if ever you met one: public class E { public struct N1 { public E e; } public struct...

In Whidbey, apart from the token handle resolution APIs I mentioned earlier, there are some overloads making these APIs look a bit more complicated. Again, I am using APIs related to MethodInfo as an representitive example: Token -> Info public...

I haven't blogged for a long time because we were busy hitting ZBB for RTM milestone. I am not aware of something special to talk about so let's talk about one of the main new features in Whidbey -- the token handle resolution APIs. We have talked...

Shawn has an excellent post about Dynamic Assemblies and Declarative Security, please check it out: http://blogs.msdn.com/shawnfa/archive/2005/05.aspx

Maybe it is a little to early to jump into this talk but I think for a user starting to use LCG, he will hit this problem in the first place. When you are emitting a dynamic method and doesn't have a way to persist it, you can imagine that it could be...

I think I will start severl topics around LCG in the furture. Our PM Joel has an excellent post about various method invocations and the paragraph about LCG is a sweet start point on Lightweight Code Gen. http://blogs.msdn.com/joelpob/archive/2004...

Shreeman suggested us to publish a list of Reflection.Emit known restrictions (that is not going to be made into Whidbey). I happen to have such a list on my machine for my own reference. So I just post them out here: Cannot Emit nested enum type...

I was about to post another blog regarding to tokens and handles and generics, but our Reflection tester Haibo suggested me to talk a little about the TypeName Grammar that we added in Whidbey because a lot of external bugs are being reported on this...

We have some token APIs on Module Builder that can be used to as an optional approach as to regular Refelction.Emit APIs. They are: public TypeToken GetTypeToken(Type type) public TypeToken GetTypeToken(String name) // this looks just like ModuleBuilder...

Reflection.Emit can emit Generics! Checkout here: Here is a code sample that tells you how to emit various Generics. It is created as dev unit test by Chris King who implemented Reflection.Emit on Generics. using System; using System.Reflection;...

This is my first post. Let me start by introducing a small program that you can do with Whidbey Reflection. Here is a small app showing you how you can get all the methods in Assembly A that is referenced by Assembly B. There was no API such as GetReferencedMethods...