Using C# dynamic to call static members

re: Using C# dynamic to call static members

Gregory Chernis — Thu, 21 Apr 2011 20:49:58 GMT

With some help, worked out a way to access the constant fields too:

stackoverflow.com/.../accessing-constants-with-a-dynamic-keyword

re: Using C# dynamic to call static members

Omer Raviv — Fri, 10 Sep 2010 19:36:51 GMT

This could've been great for the various .Parse method overloads that the primitive BCL types provide (The Convert class doesn't solve everything.)

re: Using C# dynamic to call static members

David Ebbo — Sat, 09 Jan 2010 19:17:36 GMT

@Stephen: agreed, that's a nice little addition.

re: Using C# dynamic to call static members

Stephen Swensen — Sat, 09 Jan 2010 19:07:26 GMT

Thanks for this. You can take it a step further with extension methods:

<code>

static readonly Dictionary<Type, StaticMembersDynamicWrapper> _typeLookup = new Dictionary<Type, StaticMembersDynamicWrapper>();

public static dynamic StaticMembersProxy(this Type type)

{

StaticMembersDynamicWrapper smdw;

if (!_typeLookup.TryGetValue(type, out smdw))

_typeLookup[type] = smdw = new StaticMembersDynamicWrapper(type);

return smdw;

}

</code>

re: Using C# dynamic to call static members

Paul Batum — Mon, 23 Nov 2009 05:44:34 GMT

This is a nice in that it is an easy to follow example of using the DynamicObject class, but...

Even in the case where you are forced to rely on 3rd party libraries that are exposing the functionality you need as static methods, you should be able to wrap that functionality inside your own classes and then have them implement a common interface. Therefore I am skeptical about whether the above approach is actually something you would ever want to do.

re: Using C# dynamic to call static members

David Ebbo — Tue, 03 Nov 2009 18:11:22 GMT

@David Kujawski: indeed, my code above is just a proof of concept and doesn't deal with cases like method overloading. Thanks for pointing this out!

re: Using C# dynamic to call static members

David Kujawski — Tue, 03 Nov 2009 17:07:49 GMT

Nice work, this is useful, however there are two problems with your approach:

1) no handling of overloaded methods

2) incorrect handling of optional/named parameters

I can't post the code here (in the comments since it would look terrible), but I was able modify the code to check the Binder and get the Parameters for the methods of the type to correctly handle the two issues above.

Thanks for the headstart!

re: Using C# dynamic to call static members

David Ebbo — Mon, 26 Oct 2009 19:26:50 GMT

@Jérémie: the idea of static interfaces is potentially interesting. One different is that in your case, you have T has a generic type param (as in IsInstanciated<T>() where T: ICountable). But how would you 'cast' to this interface if all you had was a System.Type, in a really late bound scenario?

re: Using C# dynamic to call static members

WebGrid — Mon, 26 Oct 2009 16:41:02 GMT

Hi,

It's like Jayson says it's nice for "duct-taping" 3rd party libraries.

It saved my day! :)

re: Using C# dynamic to call static members

Jérémie Chassaing — Mon, 26 Oct 2009 15:52:27 GMT

Coincidence, three days ago I posted a 'proposal' (nothing official here...) for static interface to resolve this kind of thing in C#.

You can read it here : http://thinkbeforecoding.com/post/2009/10/21/CSharp-Static-interfaces

and here

http://thinkbeforecoding.com/post/2009/10/22/CSharp-Static-interfaces-Take-2