# Fix for issue #4946

**URL:** <https://www.ruby-forum.com/t/fix-for-issue-4946/194011>\
**Category:** IronRuby\
**Created:** [August 27, 2010, 11:00pm UTC](https://www.ruby-forum.com/t/fix-for-issue-4946/194011 "2010-08-27T23:00:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![valdar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/b5a626/32.png) [@valdar](https://www.ruby-forum.com/u/valdar)\
**Post date:** [August 27, 2010, 11:00pm UTC](https://www.ruby-forum.com/t/fix-for-issue-4946/194011/1 "2010-08-27T23:00:56Z")

</div>

Here’s my fix for issue #4946  
[http://ironruby.codeplex.com/workitem/4946](http://ironruby.codeplex.com/workitem/4946):  
da1abbdba748f0ebdb52[http://github.com/cstrahan/ironruby/commit/da1abbdba748f0ebdb5282f8557549bf260ffd61](http://github.com/cstrahan/ironruby/commit/da1abbdba748f0ebdb5282f8557549bf260ffd61)

However, I’m curious if that’s just sidestepping another problem with  
the  
Silverlight build. Before the change, CreateObject will always raise an  
exception in Silverlight if the baseType implements ISerializable -  
after  
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  
 theclass  
.Context.SetInstanceVariable_)?

-Charles