Introduction
There are already quite a few articles about dynamic expression evaluation using .NET. What I want to show here is a new twist on the idea by using the DynamicMethod
class in the System.Reflection.Emit
namespace. In my research I've found two main ways to tackle runtime expression evaluation: compile .NET code using the System.CodeDom
namespace or write a parser. There are pros and cons with each method but I knew I didn't want to have to write a parser since .NET can already parse C# and will do a much better job at it than I can.
The good thing about compiled code is it's fast. However, there are several problems with it. It seems to take quite a bit of time to compile compared to parsing. So if the expression is constantly changing then it won't be a good performer. But if the expression is something to be compiled once and called many times then its performance can't be beat. So this is the problem I'm trying to solve; given a set of expressions I need to execute them quickly for a given set of values or row of data. Then be able to do the same for a data set by repeating for each row in the set.
Background
Some useful articles/sites I've found:
Parsing the IL of a Method Body
Turn MethodInfo to DynamicMethod
The expression evaluator revisited (Eval function in 100% managed .net)
Evaluating Mathematical Expressions by Compiling C# Code at Runtime
A Math Expression Evaluator
It would be a good idea to look at some of these to get an idea of how this article differs or on what concepts it's based.
So a problem with CodeDom is that compiling causes the resultant assembly to be loaded into the current AppDomain. Since in .NET you can't unload an assembly you would end up with a lot of assemblies since a new one is created for each new expression. To keep the generated assembly from being loaded right away another AppDomain can be created where code the is generated. But when we want to execute the expression the assembly still has to be loaded. So what can we do to get around this problem? Enter System.Reflection.Emit.DynamicMethod
class to save the day.
By now I'm sure you just looked in MSDN to find out more about it. DynamicMethod
allows a method to be created at runtime and have the speed of compiled code. This is great but just one problem: you need to write the IL code for it.
I knew I didn't want to write a parser and I sure didn't want to spend a lot of time with writing IL code. The bright idea comes from the Turn MethodInfo to DynamicMethod article linked above. Basically reflection can be used to get the IL code of a compiled method and generate a DynamicMethod
from it. Perfect! Now we can write .NET code, compile it, get the IL code and create the DynamicMethod
we need.
Using the code
To turn a MethodInfo
into a DynamicMethod
I needed to know what method was being used. I know I wanted access to functions in the same class as the method, so I didn't need to prefix with a class name. I wanted to provide a set of documented functions to the user without them having to know a lot of .NET. So I created an object with some functions on it and called it FunctionClass
.
public class FunctionClass
{
public double X;
public double Y;
public double Z;
public double Round(double number)
{
return Math.Round(number);
}
}
CodeDom Compiler
So to compile a C# expression that will have access to the methods on this class I'm going to make the compiled method on a class that inherits from FunctionClass
. This way it will have access to all protected and public methods from the base class and call them without any type prefix. The assumption I've made is that an expression is one line of code so it looks like return [user code line];
. To keep it type safe I'm also going to require that the user pick a return type for the expression; double
, string
, DateTime
, etc. So below is the code for the compiler class.
public class CSharpExpressionCompiler : BaseExpressionCompiler,
IExpressionCompiler
{
public DynamicMethodState CompileExpression(string expression,
Type functionType, Type returnType)
{
DynamicMethodState methodState;
CodeDomProvider codeProvider =
CodeDomProvider.CreateProvider("CSharp");
CompilerParameters loParameters = new CompilerParameters();
loParameters.ReferencedAssemblies.Add("System.dll");
loParameters.ReferencedAssemblies.Add(functionType.Assembly.Location);
loParameters.GenerateInMemory = true;
loParameters.TreatWarningsAsErrors = true;
string dynamicNamespace = "ExpressionEval.Functions.Dynamic";
string source = @"
using System;
using {5};
namespace {6}
{{
public class {0} : {1}
{{
public {2} {3}()
{{
return {4};
}}
}}
}}
";
string className = "Class_" + Guid.NewGuid().ToString("N");
string methodName = "Method_" + Guid.NewGuid().ToString("N");
string returnTypeName = returnType.FullName;
....
string codeString = string.Format(source, className,
functionType.FullName, returnTypeName,
methodName, expression, functionType.Namespace, dynamicNamespace);
CompilerResults results =
codeProvider.CompileAssemblyFromSource(loParameters, codeString);
if (results.Errors.Count > 0)
{
throw new CompileException(results.Errors);
}
else
{
Type dynamicType = results.CompiledAssembly.GetType(
dynamicNamespace + "." + className);
MethodInfo dynamicMethod = dynamicType.GetMethod(methodName);
methodState = GetMethodState(dynamicMethod);
}
return methodState;
}
}
The BaseExpressionCompiler
provides the GetMethodState
method that converts a MethodInfo
into a DynamicMethodState
. DynamicMethodState
is the class that provides a serializable form of a method's IL and metadata token offsets. Once I have that I can throw away the assembly that was created.
public abstract class BaseExpressionCompiler : MarshalByRefObject
{
protected DynamicMethodState GetMethodState(MethodInfo dynamicMethod)
{
DynamicMethodState methodState = new DynamicMethodState();
MethodBody methodIlCode = dynamicMethod.GetMethodBody();
methodState.CodeBytes = methodIlCode.GetILAsByteArray();
methodState.InitLocals = methodIlCode.InitLocals;
methodState.MaxStackSize = methodIlCode.MaxStackSize;
IDictionary<int, LocalVariable> locals = new SortedList<int,
LocalVariable>();
foreach (LocalVariableInfo localInfo in methodIlCode.LocalVariables)
{
locals.Add(localInfo.LocalIndex, new
LocalVariable(localInfo.IsPinned,
localInfo.LocalType.TypeHandle));
}
methodState.LocalVariables = locals;
TokenOffset tokenOffset = new TokenOffset();
IlReader reader = new IlReader(methodState.CodeBytes,
dynamicMethod.Module);
tokenOffset.Fields = reader.Fields;
tokenOffset.Methods = reader.Methods;
tokenOffset.Types = reader.Types;
tokenOffset.LiteralStrings = reader.LiteralStrings;
methodState.TokenOffset = tokenOffset;
return methodState;
}
}
The compiler class inherits from MarshalByRefObject
because it needs to be used across an AppDomain as explained earlier. Now that there is a compiler to get a DynamicMethodState
we then need to create the DynamicMethod
object from it.
DynamicMethod Delegate
The ExpressionDelegateFactory
calls to the compiler across an AppDomain it creates to compile an expression. It then creates a delegate from the DynamicMethodState
returned by the compiler in the form of R ExecuteExpression<R,C>(C functionClass)
where R is the return type and C is the function class type.
public class ExpressionDelegateFactory : IExpressionDelegateFactory
{
private ExpressionLanguage m_language;
public ExpressionDelegateFactory(ExpressionLanguage language)
{
m_language = language;
}
public ExecuteExpression<R, C> CreateExpressionDelegate<R,
C>(string expression)
{
ExecuteExpression<R, C> expressionDelegate = null;
DynamicMethodState methodState;
methodState = CreateExpressionMethodState<R, C>(expression);
if (methodState != null && methodState.CodeBytes != null)
{
expressionDelegate = CreateExpressionDelegate<R,
C>(methodState);
}
return expressionDelegate;
}
public DynamicMethodState CreateExpressionMethodState<R,
C>(string expression)
{
DynamicMethodState methodState;
IExpressionCompiler compiler;
AppDomainSetup loSetup = new AppDomainSetup();
loSetup.ApplicationBase = AppDomain.CurrentDomain.BaseDirectory;
AppDomain loAppDomain =
AppDomain.CreateDomain("CompilerDomain", null, loSetup);
string className = null;
switch(m_language)
{
case ExpressionLanguage.CSharp:
className = "CSharpExpressionCompiler";
break;
case ExpressionLanguage.VisualBasic:
className = "VisualBasicExpressionCompiler";
break;
case ExpressionLanguage.JScript:
className = "JScriptExpressionCompiler";
break;
}
compiler=(IExpressionCompiler)loAppDomain.CreateInstanceFromAndUnwrap(
"ExpressionEval.ExpressionCompiler.dll",
"ExpressionEval.ExpressionCompiler." + className);
try
{
methodState = compiler.CompileExpression(expression, typeof(C),
typeof(R));
}
catch (CompileException e)
{
StringBuilder exceptionMessage = new StringBuilder();
foreach (CompilerError error in e.CompileErrors)
{
exceptionMessage.Append("Error# ").Append(error.ErrorNumber);
exceptionMessage.Append(", column ").Append(error.Column);
exceptionMessage.Append(", ").Append(error.ErrorText);
exceptionMessage.Append(Environment.NewLine);
}
throw new ApplicationException(exceptionMessage.ToString());
}
finally
{
AppDomain.Unload(loAppDomain);
}
if (methodState != null && methodState.CodeBytes == null)
{
methodState = null;
}
return methodState;
}
public ExecuteExpression<R, C> CreateExpressionDelegate<R,
C>(DynamicMethodState methodState)
{
ExecuteExpression<R, C> expressionDelegate;
DynamicMethod dynamicMethod = new DynamicMethod(
"_" + Guid.NewGuid().ToString("N"), typeof(R),
new Type[] { typeof(C) }, typeof(C));
DynamicILInfo dynamicInfo = dynamicMethod.GetDynamicILInfo();
dynamicMethod.InitLocals = methodState.InitLocals;
SignatureHelper locals = SignatureHelper.GetLocalVarSigHelper();
foreach (int localIndex in methodState.LocalVariables.Keys)
{
LocalVariable localVar = methodState.LocalVariables[localIndex];
locals.AddArgument(Type.GetTypeFromHandle(localVar.LocalType),
localVar.IsPinned);
}
dynamicInfo.SetLocalSignature(locals.GetSignature());
IlTokenResolver tokenResolver = new IlTokenResolver(
methodState.TokenOffset.Fields,
methodState.TokenOffset.Methods,
methodState.TokenOffset.Types,
methodState.TokenOffset.LiteralStrings);
methodState.CodeBytes = tokenResolver.ResolveCodeTokens(
methodState.CodeBytes, dynamicInfo);
dynamicInfo.SetCode(methodState.CodeBytes, methodState.MaxStackSize);
expressionDelegate = (ExecuteExpression<R,
C>)dynamicMethod.CreateDelegate(
typeof(ExecuteExpression<R, C>));
return expressionDelegate;
}
}
The 'magic' for DynamicMethod
is that it behaves like a static method except it can also be used like an instance method. In IL code the first argument in an instance method is always the instance of the type to which the method belongs. So to trick this static method to behave like an instance, you make sure the first argument of the method is an instance of the type to which the method belongs. Read about this in MSDN because its the important concept that makes this code work.
I also wanted to hide the implementation of creating a DynamicMethod
from the code using the expression so I created an ExpressionEvaluator
that wraps the calls to the ExpressionDelegateFactory
. The code is separated into 5 different projects: MsilConversion (IL reading and token resolving), MethodState (shared dll between app domains, DynamicMethodState), ExpressionCompiler (langauge specific compilers), DynamicMethodGenerator (DynamicMethod delegate factory), ExpressionEvaluation (wrapper around delegate factory).
I created a Windows Forms test application aptly named TestApp to call the ExpressionEvaluation engine. It has a simple one-time Evaluate and then a Loop function that shows the performance that a 'compile once, run many times' operation can achieve.
Possibilities
There appear to be quite a few possibilities from here for implementation enhancements or changes. Different .NET languages, a language translator from custom language to .NET language, supporting multiple code lines instead of a one line expression. Maybe being even more ambitious and creating a parser/IL generator to skip the CodeDom step and write IL directly.
Feedback
I would appreciate any feedback you can give me on the code, concept, or the article itself. Also, I'm curious about your ideas for enhancements and if you implement this concept what was the result.
History
- 3/13/2007 - First Published