Try the following code with a .Net 3.5 setting
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text; namespace ClassLibrary1
{
public class Class1
{
public void Do()
{
Funcstring f = () = ;
}
}
}
*This is what I
You'll need to alias Microsoft.Scripting.Core.dll when you're building a 3.5
project. From the command line this is
Csc /reference:MSCore=Microsoft.Scripting.Core.dll ...
And then you can refer to these namespaces as starting w/ MSCore. Alternately
you can leave out the System.Core
On Fri, Aug 15, 2008 at 9:37 AM, Dino Viehland [EMAIL PROTECTED] wrote:
You'll need to alias Microsoft.Scripting.Core.dll when you're building a 3.5
project. From the command line this is
Csc /reference:MSCore=Microsoft.Scripting.Core.dll …
Any idea how to do this in Visual Studio?
FastCallable's certainly the right spot if anything will come close. My main
concern is that it'll probably leave a lot of stuff out...
In 2.0 this is actually easier. You could modify the DLR in MetaAction.cs to
wrap every single dynamic operation - whether that be addition, calling
Thanks, I'll have a look at that. Hopefully it will help the effort of
porting Resolver One to IP2.
Dino Viehland wrote:
FastCallable's certainly the right spot if anything will come close. My main
concern is that it'll probably leave a lot of stuff out...
In 2.0 this is actually easier.
Ah cool. I forgot this little feature of C# 2.0. Thanks a lot.
Dody G.
On Fri, Aug 15, 2008 at 7:47 PM, Dino Viehland [EMAIL PROTECTED] wrote:
For the aliased references it looks like if you go to properties for the
individual reference in the solution explorer there's an Alisies property.
Ok, I looked into a bunch of these and here's what I've discovered so far and
other random comments...
Exceptions (10): 40% slower
IP1: 4703
IP2: 6125
Py: 266
I haven't looked at this one yet. I do know that we have a number of bug fixes
for our exception handling which will
Dino Viehland wrote:
Ok, I looked into a bunch of these and here's what I've discovered so far and
other random comments...
Exceptions (10): 40% slower
IP1: 4703
IP2: 6125
Py: 266
I haven't looked at this one yet. I do know that we have a number of bug fixes
for our
Have you tried using the VS profiler on a precompiled dll? I don't know how
well it works, but VS profiler needs IL on disk, and with precompilation, you
have that. There is still IL generated on the fly for rules, but you might be
able to get some reasonable numbers.
Thanks,
Shri
