Microsoft.Scripting.Core.dll is effectively a subset of .NET 4.0's System.Core.dll, which is why there's so much overlap in the types. For IronPython, we've worked around this by creating an automated process to rename all the types from System.* to Microsoft.*. But this doesn't work as well for Ruby because Ruby allows for outside contributions. Improving this situation is of definite interest to us.
This problem goes away once .NET 4.0 ships, provided IronRuby is built against it. From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Ivan Porto Carrero Sent: Friday, January 30, 2009 3:18 AM To: ironruby-core@rubyforge.org Subject: [Ironruby-core] progress on ironrubymvc :) <snip> Also there is a conflict between 2 types in the System namespace. System.Func is defined in 2 places. I aliased the System.Core assembly and am using the type from System.Core. This does give some weird results because apparently System.Func<>, System.Core,..,... and System.Func<>, System.Core aren't the same when the mvc framework checks for the types of the parameter. Any tips to get around this? Am I doing something wrong? <snip> Cheers Ivan
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
