First, many thanks to the IronRuby team and their outstanding work on
Now, my question: I want to embed both IronRuby and IronPython in my
application. In the past, in order to avoid
namespace/assembly/version collisions, I’ve just downloaded one of the
builds from one team or the other that includes both sets of binaries.
However, yesterday, all the planets aligned, and both teams released a
I’ve been waiting for (IronRuby 1.0 and IronPython 2.6.1).
What is the best way for me to keep in sync with both teams’ releases?
there a coordinated build that is released on a regular basis? I did try
downloading the DLR sources and building from scratch. It appears
is up to 2.6.1 in the DLR source, but IronRuby is still reporting
IronPython and IronRuby not only released on the same date, but we
released out of the same branch, so we have dependencies on the same
exact DLR; a first in the project’s history. This is why IronRuby didn’t
release a “for IronPython interop” package.
Going forward, we will not always be this fortunate to sync up releases.
This time around we decided to snap to .NET 4.0’s releases, but that
only happens every couple years, so not a great release strategy for us.
In general, it’s best to pull sources from dlr.codeplex.com if you
absolutely need binaries that work together. Keep in mind you can also
get the sources from github.com/ironruby/ironruby, as they include
IronPython’s sources as well (Merlin/main/languages/IronPython).
Unfortunately, neither repository is up to date with our main branch,
though ironruby’s 1.0 branch is exactly the sources for 1.0. This is
because our CI lab is being moved to another building, and we’ve yet to
get it back up, so the source publishing hasn’t been happening. It will