Fix for issue #4946

Here’s my fix for issue #4946

However, I’m curious if that’s just sidestepping another problem with
Silverlight build. Before the change, CreateObject will always raise an
exception in Silverlight if the baseType implements ISerializable -
the change, it won’t throw when the baseType is RubyObject. Shouldn’t
we always
ignore the ISerializable attribute in the Silverlight build and instead
default to the second part of the if/else (the part where we use



This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs