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, which has current IronRuby bits working against a rewritten version of Microsoft.Scripting.Core.dll.
~js > -----Original Message----- > From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core- > boun...@rubyforge.org] On Behalf Of Aaron Clauson > Sent: Monday, April 13, 2009 7:29 PM > To: ironruby-core@rubyforge.org > Subject: [Ironruby-core] Namespace Conflict System.Linq > > 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 > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
