Is there a workaround that we can use in the time being? I found where the exception was being thrown and tried to figure it out myself, but the codebase is just too foreign me.
Thanks, Zach Jimmy Schementi wrote: > That's because the bug still exist ... > http://ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=578 > > ~js -- Posted via http://www.ruby-forum.com/. _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
