Re: [IronPython] Compiling IronPython for .NET 3.5

2011-05-06 Thread Raghavendra Chandrashekara
Hi, I downloaded the latest snapshot from github and used the Solutions\Dlr.sln file to build the v2Release configuration. There were a couple of compilation errors, no Complex object in .NET 3.5, and no StringBuilder.Clear() method which were easy enough to get around. After the changes (I hope I

Re: [IronPython] Compiling IronPython for .NET 3.5

2011-05-06 Thread Raghavendra Chandrashekara
I was originally trying to build Solutions\IronPython.sln. I think I should have been building Solutions\Dlr.sln (which does contain configurations for v2Release and v2Debug). Is this the correct solution file I should be building? If so, then after doing a build I get the following errors: --

Re: [IronPython] Compiling IronPython for .NET 3.5

2011-05-06 Thread Slide
You may need to get latest rather than the 2.7 snapshot. On May 6, 2011 8:16 PM, "Raghavendra Chandrashekara" < raghavendra.chandrashek...@gmail.com> wrote: > Hi Tomas, > > But there is no v2Debug or v2Release configuration. All I see is Debug, > Release, Silverlight4Debug, and Silverlight4Release.

Re: [IronPython] Compiling IronPython for .NET 3.5

2011-05-06 Thread Raghavendra Chandrashekara
Hi Tomas, But there is no v2Debug or v2Release configuration. All I see is Debug, Release, Silverlight4Debug, and Silverlight4Release. Did I download the incorrect version of the source code? Thanks, Raj On Fri, May 6, 2011 at 9:45 PM, Tomas Matousek wrote: > Do not change any project settin

Re: [IronPython] Compiling IronPython for .NET 3.5

2011-05-06 Thread Tomas Matousek
Do not change any project settings. Just select build configuration "v2Debug" or "v2Release". The default configuration "Debug" builds for V4. Tomas From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Raghavendra Chandrashekara Sent: Friday, May 06

Re: [IronPython] Compiling IronPython for .NET 3.5

2008-09-26 Thread Curt Hagenlocher
No, you haven't done anything wrong. I never tested those instructions when Harry asked me to proof them, and forgot that the namespace hackery that we did for InteropServices would cause a conflict if you were to link against both System.Core and Microsoft.Scripting.Core. We're currently investi