v2Debug” or “v2Release”. The default configuration “Debug” builds for
> V4.
> >>
> >>
> >>
> >> Tomas
> >>
> >>
> >>
> >> *From:* users-boun...@lists.ironpython.com [mailto:
> >> users-boun...@lists.ironpython.co
nks,
>
> Raj
>
> On Fri, May 6, 2011 at 9:45 PM, Tomas Matousek <
> tomas.matou...@microsoft.com> wrote:
>
>> Do not change any project settings. Just select build configuration
>> “v2Debug” or “v2Release”. The default configuration “Debug” builds for V4.
>>
&
avendra
>> Chandrashekara
>> *Sent:* Friday, May 06, 2011 5:26 PM
>> *To:* users@lists.ironpython.com
>> *Subject:* [IronPython] Compiling IronPython for .NET 3.5
>>
>>
>>
>> Hi All,
>>
>> I am trying to compile IronPython for .NET Framework v 3.5.
ekara
> *Sent:* Friday, May 06, 2011 5:26 PM
> *To:* users@lists.ironpython.com
> *Subject:* [IronPython] Compiling IronPython for .NET 3.5
>
>
>
> Hi All,
>
> I am trying to compile IronPython for .NET Framework v 3.5. I have
> downloaded the source code from
> htt
andrashekara
Sent: Friday, May 06, 2011 5:26 PM
To: users@lists.ironpython.com
Subject: [IronPython] Compiling IronPython for .NET 3.5
Hi All,
I am trying to compile IronPython for .NET Framework v 3.5. I have downloaded
the source code from https://github.com/IronLanguages/main/zipball/ipy-2.7.
Hi All,
I am trying to compile IronPython for .NET Framework v 3.5. I have
downloaded the source code from
https://github.com/IronLanguages/main/zipball/ipy-2.7. After opening the
IronPython solution file I tried to change the target framework to 3.5 in
the IronPython project properties page. Afte
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
Thanks to the team for facing the heavy changes that were required to
improve the compatibility of IronPython and DLR with projects that target
.NET Framework 3.5. From Harry's account[1], we can see that it took a lot
of smarts and guts to do.
[1] http://devhawk.net/2008/09/17/DLR+Namespace+Chang
