# IronRuby Binaries and Known DLR build

**URL:** <https://www.ruby-forum.com/t/ironruby-binaries-and-known-dlr-build/138612>\
**Category:** IronRuby\
**Created:** [May 25, 2008, 10:12pm UTC](https://www.ruby-forum.com/t/ironruby-binaries-and-known-dlr-build/138612 "2008-05-25T22:12:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![benhiller](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/8e7dd6/32.png) [@benhiller](https://www.ruby-forum.com/u/benhiller)\
**Post date:** [May 25, 2008, 10:12pm UTC](https://www.ruby-forum.com/t/ironruby-binaries-and-known-dlr-build/138612/1 "2008-05-25T22:12:55Z")

</div>

Hello,

Scenario. I want to host the DLR within my application, as such I  
reference MS.Scripting and MS.Scripting.Core. I can then happily  
reference IP2 because it was compiled against the same version.

However, the same can’t be said for IronRuby. Because there aren’t any  
binaries available to download (Unless I am mistaken, I read they were  
going to be added to the repos but I couldn’t them) and because you  
are building from the DLR source instead of known releases it looks  
like i’m going to need two copies of the DLR assemblies within my  
application.

An example of where this is a problem, TokenizerService is within the  
DLR for IronRuby but not for IronPython.

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?

Thanks

Ben  
[Blog.BenHall.me.uk](http://Blog.BenHall.me.uk)

---

<div class="post-metadata">

**Author:** ![benhiller](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/8e7dd6/32.png) [@benhiller](https://www.ruby-forum.com/u/benhiller)\
**Post date:** [May 25, 2008, 11:53pm UTC](https://www.ruby-forum.com/t/ironruby-binaries-and-known-dlr-build/138612/2 "2008-05-25T23:53:18Z")

</div>

We don’t currently host binaries, in part because it hasn’t been set up,  
and in part because IR is such a fast moving target right now. After  
RailsConf we can figure out what and where to host some stuff.

Jim D.

* * *

From: removed\_email\_address@domain.invalid  
[removed\_email\_address@domain.invalid] On Behalf Of Ben H.  
[removed\_email\_address@domain.invalid]  
Sent: Sunday, May 25, 2008 1:09 PM  
To: removed\_email\_address@domain.invalid  
Subject: [Ironruby-core] IronRuby Binaries and Known DLR build

Hello,

Scenario. I want to host the DLR within my application, as such I  
reference MS.Scripting and MS.Scripting.Core. I can then happily  
reference IP2 because it was compiled against the same version.

However, the same can’t be said for IronRuby. Because there aren’t any  
binaries available to download (Unless I am mistaken, I read they were  
going to be added to the repos but I couldn’t them) and because you  
are building from the DLR source instead of known releases it looks  
like i’m going to need two copies of the DLR assemblies within my  
application.

An example of where this is a problem, TokenizerService is within the  
DLR for IronRuby but not for IronPython.

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?

Thanks

Ben  
[Blog.BenHall.me.uk](http://Blog.BenHall.me.uk)

* * *

Ironruby-core mailing list  
removed\_email\_address@domain.invalid  
[http://rubyforge.org/mailman/listinfo/ironruby-core](http://rubyforge.org/mailman/listinfo/ironruby-core)