[IronPython] IronPython + IronRuby + Known DLR Build

Dave Fugate dfugate at microsoft.com
Tue May 27 17:55:40 CEST 2008

Internally, IronPython and IronRuby are always built against the latest version of the DLR.  The reason it looks like they're built on different versions is simply due to different release intervals for the two languages.

You're correct that the DLR will eventually stabilize and both IronPython/IronRuby will be buildable against a set version of the DLR (e.g., DLR 1.0).

In the short term, I'll talk to the IronRuby guys and see if we can synchronize weekly uploads to IronPython's TFS server and IronRuby's Subversion repository.

-----Original Message-----
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Ben Hall
Sent: Sunday, May 25, 2008 2:55 PM
To: Discussion of IronPython
Subject: [IronPython] IronPython + IronRuby + Known DLR Build


Posted similar message onto IronRuby but I thought I would also ask
you guys. My scenario is that I need to host IronRuby and IronPython
within the same application. I thought this would be easy as they both
are based on the DLR.

However, you both appear to be at different stages of the DLR life and
building against different sources.  Is this the same internally? At
the moment I can't see a way I can build both IronPython and IronRuby
from the same DLR assemblies?

At some point, I take it the DLR will merge into a single release and
known assembly for other language providers and hosts to use instead
of multiple different versions?

In the mean time - what can I do?  Is anyone doing this?


Users mailing list
Users at lists.ironpython.com

More information about the Ironpython-users mailing list