Thanks for the reply. Here's what I tried:
1. Download the latest source.
2. Open the solution in VS2010.
3. Change target for Jurassic.dll to .Net Framework 4
4. Build Jurassic.dll
5. Reference Jurassic.dll from a simple console app, which does this:
static void Main(string args)
ScriptEngine engine = new ScriptEngine();
object r = engine.Evaluate("x = 100;");
The first thing that happens, when the console application is executed, is that the system complains about GetObjectData not being marked with [SecurityCritical] and so I went through and marked all of the GetObjectData implementations with that attribute.
If I go ahead and then mark all the GetObjectData implementations with the [SecurityCritical] attribute, that takes care of the first exception, but then the system complains about line 127 in DynamicIlGenerator.cs and throws the following exception:
Message=Operation could destabilize the runtime.
at Jurassic.Compiler.DynamicILGenerator.Complete() in C:\tmp\jurassic\jurassic_2359aadc27fe\Jurassic\Compiler\Emit\ILGenerator\DynamicILGenerator.cs:line 127
I'm running this as Administrator on my local desktop, from the local drive, so not sure about any permission issues this relates to.
I'm sure I can go ahead with the 3.5 binaries (this doesn't happen when I target 3.5, just when I change Jurassic.dll to 4.0), I was just hoping there was an easy way to target 4.0 as part of my Azure project.
Thanks for any suggestions, and I hope you keep up the great work - this is a great project!