# IronRuby and IronPython

**URL:** <https://www.ruby-forum.com/t/ironruby-and-ironpython/186865>\
**Category:** IronRuby\
**Created:** [April 13, 2010, 4:42pm UTC](https://www.ruby-forum.com/t/ironruby-and-ironpython/186865 "2010-04-13T16:42:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Justin\_H.man](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/4af34b/32.png) [@Justin\_H.man](https://www.ruby-forum.com/u/Justin_H.man)\
**Post date:** [April 13, 2010, 4:42pm UTC](https://www.ruby-forum.com/t/ironruby-and-ironpython/186865/1 "2010-04-13T16:42:13Z")

</div>

Hi all,

First, many thanks to the IronRuby team and their outstanding work on  
the  
1.0 release!

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  
build  
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?  
Is  
there a coordinated build that is released on a regular basis? I did try  
downloading the DLR sources and building from scratch. It appears  
IronPython  
is up to 2.6.1 in the DLR source, but IronRuby is still reporting  
0.9.something.

Many thanks,

```
 -Justin
```

---

<div class="post-metadata">

**Author:** ![Justin\_H.man](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/4af34b/32.png) [@Justin\_H.man](https://www.ruby-forum.com/u/Justin_H.man)\
**Post date:** [April 14, 2010, 10:02am UTC](https://www.ruby-forum.com/t/ironruby-and-ironpython/186865/2 "2010-04-14T10:02:33Z")

</div>

Your welcome 🙂

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](http://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](http://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  
resume shortly.

~Jimmy