Hi, Jeff,
Von: Jeff Hardy [mailto:jdha...@gmail.com]
> On Thu, Jul 28, 2011 at 12:07 AM, Markus Schaber software.com> wrote:
> >> [Compiling IPy 2.7 for a pure .NET 2.0]
> >
> > I did try to patch some of the problems
> >
> > g...@github.com:markusschaber/IronLanguages.git (2.7-maint branch)
> >
Hi, Jeff,
Von: Jeff Hardy
> I don't know why Markus' clients can't/won't upgrade to 3.5, but I'm
sure
> they're not good reasons. :)
Well, some of our clients are OEMs shipping very customized versions of
our product. Some of them urge us to update to .NET 4.0 for some
reasons, others urge us to
On Thu, Jul 28, 2011 at 12:07 AM, Markus Schaber
wrote:
> Hi,
>
>> [Compiling IPy 2.7 for a pure .NET 2.0]
>
> I did try to patch some of the problems
>
> g...@github.com:markusschaber/IronLanguages.git (2.7-maint branch)
>
> Now I have about 270 problems mostly relating to extension methods,
> ma
On Thu, Jul 28, 2011 at 12:44 AM, Doug Blank wrote:
> It was rumored that Ubuntu might be getting a more recent Mono soon,
> but it would still be nice to clean this up a bit. Is v2Release really
> v3.5Release?
Yes.
- Jeff
___
Ironpython-users mailing
On Thu, Jul 28, 2011 at 6:40 AM, Jimmy Schementi wrote:
> I'm a little confused about the issues, as with this simple patch:
> https://gist.github.com/557
>
> I'm able to build IronPython (using IronPython.Mono.sln as that still
> has v2Debug build configurations):
> msbuild Solutions\IronPyth
I'm a little confused about the issues, as with this simple patch:
https://gist.github.com/557
I'm able to build IronPython (using IronPython.Mono.sln as that still
has v2Debug build configurations):
msbuild Solutions\IronPython.Mono.sln /p:Configuration=v2Debug
And run it, showing it's using
Hi,
Von: Markus Schaber
> > > [Compiling IPy 2.7 for a pure .NET 2.0]
> >
> > I did try to patch some of the problems
> >
> > g...@github.com:markusschaber/IronLanguages.git (2.7-maint branch)
> >
> > Now I have about 270 problems mostly relating to extension methods,
> > maybe I will find enough
Hi,
> > [Compiling IPy 2.7 for a pure .NET 2.0]
>
> I did try to patch some of the problems
>
> g...@github.com:markusschaber/IronLanguages.git (2.7-maint branch)
>
> Now I have about 270 problems mostly relating to extension methods, maybe
> I will find enough time to fix some of them this eve
On Thu, Jul 28, 2011 at 3:07 AM, Markus Schaber
wrote:
> Hi,
>
>> [Compiling IPy 2.7 for a pure .NET 2.0]
>
> I did try to patch some of the problems
>
> g...@github.com:markusschaber/IronLanguages.git (2.7-maint branch)
>
> Now I have about 270 problems mostly relating to extension methods,
> may
Hi,
> [Compiling IPy 2.7 for a pure .NET 2.0]
I did try to patch some of the problems
g...@github.com:markusschaber/IronLanguages.git (2.7-maint branch)
Now I have about 270 problems mostly relating to extension methods,
maybe I will find enough time to fix some of them this evening.
Is it ev
Hi, Jeff,
Von: Jeff Hardy [mailto:jdha...@gmail.com]
>
> Also, there might be some changes that require 3.5 (use of Linq, etc.)
> since I don't know if anyone was testing on plain-old .NET 2.0 (I
think
> the v2 targets are actually set for 3.5). There are supposed to be
targets
> on the build ser
Hi, Jimmy,
Von: Jimmy Schementi [mailto:jscheme...@gmail.com]
> On Jul 27, 2011, at 2:28 AM, Markus Schaber wrote:
>> It seems that IronPython 2.7 beta 2 can only be compiled for .NET 3.5, but
>> will not work any more when the projects are converted to be pure .NET 2.0
>> projects (using Shar
Also, there might be some changes that require 3.5 (use of Linq, etc.)
since I don't know if anyone was testing on plain-old .NET 2.0 (I
think the v2 targets are actually set for 3.5). There are supposed to
be targets on the build server that build .NET 2, but I'm not sure if
they're working. Of co
On Wed, Jul 27, 2011 at 9:01 AM, Vernon Cole wrote:
> I am using this as a renewal of my request/suggestion that we revisit
> the decision to not supply a .NET 2.0 version of IronPython 2.7.
I'm considering doing a zip-only release of 2.7.1 for .NET 2 for the
reasons that you give. I need to fix
We do still have the v2Debug build configuration available in the csproj files,
and IronPython.Mono.sln still allows building it:
msbuild Solutions\IronPython.Mono.sln /p:Configuration=v2Debug
However, current sources fail to build in a few places. Looks like you can put
#if !CLR2 around those a
I am using this as a renewal of my request/suggestion that we revisit
the decision to not supply a .NET 2.0 version of IronPython 2.7.
The current shipping version of Ubuntu has the .NET 2.0 compatible
version of MONO, and cannot easily be upgraded. It cannot be used to
build IronPython, so user
Hi,
It seems that IronPython 2.7 beta 2 can only be compiled for .NET 3.5,
but will not work any more when the projects are converted to be pure
.NET 2.0 projects (using SharpSVN).
Is this a known issue?
Or is there an error on my side?
Thanks,
Markus
Best regards
Markus Schab
17 matches
Mail list logo
