# Namespace Conflict System.Linq

**URL:** <https://www.ruby-forum.com/t/namespace-conflict-system-linq/165454>\
**Category:** IronRuby\
**Created:** [April 14, 2009, 4:29am UTC](https://www.ruby-forum.com/t/namespace-conflict-system-linq/165454 "2009-04-14T04:29:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![acampos](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/919ad9/32.png) [@acampos](https://www.ruby-forum.com/u/acampos)\
**Post date:** [April 14, 2009, 4:29am UTC](https://www.ruby-forum.com/t/namespace-conflict-system-linq/165454/1 "2009-04-14T04:29:19Z")

</div>

Hi,

I host an IronRuby engine in my app and get a lot of compiler warnings  
about duplicate definitions for classes in System.Linq. In the past it  
wasn’t much of an issue but now that I have started using some Linq  
functionality I have found myself having to add and remove System.Linq  
and Microsoft.Scripting.Core to get my app to compile. It seems that  
when there is a conflict the assembly reference added last wins.

Is there a better way to solve this? Are the DLR and main .Net Linq  
namespaces going to merge in the future?

Thanks,

Aaron

---

<div class="post-metadata">

**Author:** ![acampos](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/919ad9/32.png) [@acampos](https://www.ruby-forum.com/u/acampos)\
**Post date:** [April 15, 2009, 12:40am UTC](https://www.ruby-forum.com/t/namespace-conflict-system-linq/165454/2 "2009-04-15T00:40:27Z")

</div>

Yes, they are going to merge. However, I’m pretty sure there’s no good  
way to get rid of the warnings without us having to rewrite the  
namespaces of Microsoft.Scripting.Core.dll. If you really want to get  
rid of those warnings, you can grab IronRuby from  
[http://dlr.codeplex.com](http://dlr.codeplex.com), which has current IronRuby bits working against  
a rewritten version of Microsoft.Scripting.Core.dll.

~js