Issue with ExpandoObject and ClearScript about clearscript HOT 2 CLOSED

Hi @kevinkoenig,

Thanks for providing all that information. We believe that the behavior you're seeing is by design.

1. The "extra" methods are inherited from the ultimate base class System.Object. In the managed domain these methods are unusual in that they're always accessible, even when the static type is anonymous, external, dynamic, an interface, etc.

2. The exceptions are due to the way dynamic objects work in ClearScript. When the script engine requests member evaluation for a dynamic object, ClearScript first attempts to fulfill the request via the object's IDynamicMetaObjectProvider implementation. For members defined statically, such as normal compiled methods, this attempt fails and an exception is thrown. ClearScript catches the exception and falls back to normal member binding. In other words, the exception should be handled internally without affecting your application, and in the debugger it should be safe to disable first-chance handling for the exception type ("Break when this exception type is thrown").

from clearscript.

First let me just thank you all for the quick responses. The support on this library is really great.

I normally run with all exceptions on in our core product as I find that many people ignore real issues that are swallowed using exceptions. Then I turn them off as I understand them.

I probably spent 3 days trying to debug the issue assuming there was something wrong with my application. I can say I learned a lot about dynamics and how ClearScript supports them, so the time wasn't entirely wasted 👍.

I guess the issue is that while I was debugging inside ClearScript a request timed out which caused @code to display 'unknown' for every member of the object I as returning.

I have it all back together now and it is working perfectly (now that I disabled those exceptions)

Kevin

from clearscript.