On 15/04/2010 00:53, Jimmy Schementi wrote:
>>> Did you see the report of my problem with the RichTextBox with
IronPython 2.6.1 RC. Do you see the same problem?
Yes, I can repro it using *both* IronPython binaries built against SL3
and SL4; it appears that the RichTextBox.ctor() fails to be called via
reflection. We call via reflection in the interpreter first as an
optimization, and then generate code to do the call; though it looks
like both paths are failing. I’m looking into this … installing windbg
on my new machine at the moment =P
Thanks very much Jimmy. Do you want me to open a bug on codeplex to
track this? In the meantime I'm writing some C# to instantiate a
RichTextBox and return it to us.
All the best,
Michael Foord
>>> The person who started this thread reported not being able to
reference the assemblies.
Oh, I thought they were trying to add references to the .NET 4.0 built
assemblies in a Silverlight project, which absolutely doesn’t work;
you need to use a build for Silverlight.
*From:* Michael Foord [mailto:fuzzy...@voidspace.org.uk]
*Sent:* Wednesday, April 14, 2010 2:41 PM
*To:* Discussion of IronPython
*Cc:* Jimmy Schementi
*Subject:* Re: [IronPython] IronPython 2.6.1 for .NET 4.0 RC targeting
Silverlight
On 14/04/2010 09:29, Jimmy Schementi wrote:
[snip...]
In general versions of IronPython built against (for example)
Silverlight 2 *can* use features from Silverlight 3. (Try Python uses
IronPython that was built against Silverlight 2 - but dynamically uses
some Silverlight 3 APIs if they are available.) As Silverlight 4
includes a different version of the CLR - and not just different API
sets - I guess it particularly makes a difference if you are compiling
C# code that works with IronPython. Odd and annoying that it won't
even add references to earlier versions though. Does *everything* need
to be specially compiled to be used with .NET 4?
The *current* Silverlight builds can use SL4 features; like webcam,
etc. This is because IronPython calls .NET APIs dynamically. However,
since the Silverlight 2 builds don't statically depend on any of the
new APIs in the Silverlight 4, any CLR4 features that the
compilers/libraries usually depend on in .NET 4 aren't available in
Silverlight 4; that's what the Silverlight 4 build will do for you.
Did you see the report of my problem with the RichTextBox with
IronPython 2.6.1 RC. Do you see the same problem?
With regard to adding references to assemblies; as long as the same
APIs exist in both versions of Silverlight, it will work in both,
regardless of which compiler you use. It's the same situation with
different .NET versions. Did I miss something where someone reported
not being able to do this?
The person who started this thread reported not being able to
reference the assemblies.
All the best,
Michael Foord
_______________________________________________
Users mailing list
Users@lists.ironpython.com <mailto:Users@lists.ironpython.com>
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
--
http://www.ironpythoninaction.com/
--
http://www.ironpythoninaction.com/
_______________________________________________
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
