Just noticing this warning.. Is LoadWithPartialName
expected to remain in 2.0 since its 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'
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) because we
Hello,
I tried to build IronPython 0.9 with Mono. I used Debian package currently
in Sid to do so.
With attached patch, I succeeded building it, but it doesn't really
run. Transcript follows:
* * *
[EMAIL PROTECTED]:~/fepy$ mono --version
Mono JIT compiler version 1.1.8.2, (C) 2002-2005
the namespace System.Net.Sockets contains an enumation type named
SocketOptionName for retrieving Socket options. It's definition is:
public enum SocketOptionName
{
// Fields
AcceptConnection = 2,
AddMembership = 12,
AddSourceMembership = 15,
BlockSource = 0x11,
Hi Anthony,
I don't think it is a bug. The value you get when getting an enum value
(SocketOptionName.Broadcast) is indeed the value itself:
x = SocketOptions.Broadcast
x becomes a boxed enum object. It is the ToString() method of the enum
object prints the name. Consider following C# code that
Yes, it is a known problem. The tab-completion is far, far from finished and this is probably the first thing for me to fix - pressing tab at the beginning of the line should not offer options, but simply tab out.
Thanks for feedback!
MArtin
From: Keith J. Farmer
Sent: 8/4/2005 2:44 AM
To:
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
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 somewhat further
Hi Keith!
LoadWithPartialName may be indeed removed as the build-time warning suggests suggests. There is a good reasoning behind removing the method (what version, from where, etc ... would the method call load? I think there is a blog out there that talks more about the reasoning:
Yeah, I think you've got the priority right for my tastes: CPython parity
before CLR producer status.
Somehow, I don't think it'll take much longer for y'all.
From: [EMAIL PROTECTED] on behalf of Martin Maly
Sent: Thu 8/4/2005 12:21 PM
To: Discussion of
10 matches
Mail list logo
