long way to go to be perfect and we are trying to determine the
> importance for our users to help use choose whether to try and implement
> it for 1.0 or later.
>
> Martin
>
>
> From: Keith J. Farmer
> Sent: 8/4/2005 3:11 AM
>
On 8/4/05, Martin Maly <[EMAIL PROTECTED]> wrote:
Hi Martin,
thanks very much for the reply. Actually I think I didn't phrase my
questions very well because all I really wanted to know was:
- Will I be able to code ASP .NET v. 2 pages with IronPython?
- Will it be integrated in VS .NET 2005 IDE?
Title: RE: [IronPython] IronPython 0.9 released
Hi Martin
I hope with Lorenzo for a a version if IronPython running on .Net
1.1.
Many servers are running on .Net 1.1.
Rocco Pellegrini
- Original Message -
From:
Martin Maly
To: Lorenzo Bolognini ; Discussion of
>We haven't reached decision on this one yet and it would be
interesting to hear feedback as
>to how important having a version if IronPython running on .Net 1.1 is for you.
It would be the only way I'd get to use it at work, so I'd love to
have a 1.1 version, even if it sacrifices some support.
PM
To: Discussion of IronPython; Discussion of IronPython
Subject: RE: [IronPython] IronPython 0.9 released
As for the static compilation, it is another 'maybe' for 1.0 and we are not
decided one way or another (it is another topic you can provide feedback on and
let us k
on of IronPython
Subject: RE: [IronPython] IronPython 0.9 released
Just noticing this warning.. Is LoadWithPartialName expected to remain in 2.0 since it’s close to RTM?
'System.Reflection.Assembly.LoadWithPartialName(string)' is obsolete: 'This method has been deprecated. Plea
Title: RE: [IronPython] IronPython 0.9 released
As for the static compilation, it is another 'maybe' for 1.0 and we are not decided one way or another (it is another topic you can provide feedback on and let us know how important it is to you).
For the 0.9 I actually went somewh
Title: RE: [IronPython] IronPython 0.9 released
Hi Lorenzo,
Since the .Net 2.0 final has not yet been released, we continue to product our builds on .NET 2.0 Beta 2 which was publicly released and is, in our opinion, most widely adopted by our users. As soon as .Net 2.0 ships its final
I'm not sure where you got the idea that IronPython 1.0 only works with .NET
1.1?
I can compile the IronPython solution using the VS 2005 Beta 2 release (and
have, several times tonight). For what it's worth, IronPython needs the 2.0
runtime, since it uses 2.0 code generation, and supports 2.0
On 8/2/05, Martin Maly <[EMAIL PROTECTED]> wrote:
> Known issues:
>Rebuilding IronPython on the Community Technology Preview release,
> version 2.0.50630.0 will fix the problem. We decided to maintain the
> dependency of the released binaries on .NET 2.0 Beta 2 (version
> 2.0.50215.44) becau
Just noticing this warning.. Is LoadWithPartialName
expected to remain in 2.0 since it’s close to RTM?
'System.Reflection.Assembly.LoadWithPartialName(string)'
is obsolete: 'This method has been deprecated. Please use Assembly.Load()
instead. http://go.microsoft.com/fwlink/?linkid=14202
Title: RE: [IronPython] IronPython 0.9 released
I am not aware of any such effort being under way. We are, however, keenly aware of the need have the kind of documentation you are referring to.
Martin
From: Richard Hsu
Sent: 8/2/2005 6:22 PM
To
Congratulations to the IronPython team for releasing v0.9
The tab feature is really cool indeed. Thanks to Sumit Basu for bringing
it up.
Has anyone has started to map C# [Ecma 3rd edition] language spec to
IronPython ? I mean like feature by feature, how a C# thing can be done
in IronPython
] IronPython 0.9
released
Checked out the tab-support on the new console -
COOL! I'm going to have to peek at this code
shortly...
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Martin MalySent: Tuesday, August 02, 2005 10:20 AMTo:
users-ironpytho
bject: [IronPython]
IronPython 0.9 released
Hello IronPython
community,
it has been
exactly seven weeks since the last IronPython release - 0.7.6. Back then we
announced that the next release would take longer than our usual
two weeks, it would include some larger-scale changes, and it would be
versio
Hello IronPython community,
it has been exactly seven weeks since the last IronPython release - 0.7.6. Back then we announced that the next release would take longer than our usual two weeks, it would include some larger-scale changes, and it would be version 0.8.
The work did take couple
16 matches
Mail list logo
