Comments on: Calling a Static Method from an Object Instance in C#

By: Rajeev

Rajeev — Wed, 19 Oct 2011 08:37:12 +0000

How about this?
ddlVenue.FillValues();

method is defined as:

public static void FillValues(this DropDownList ddl)
{
ddl.DataValueField = “value”;
ddl.DataTextField = “test”;
ddl.DataBind();
}

By: Dean

Dean — Fri, 18 Dec 2009 15:10:38 +0000

Nayak, the article you linked to makes the same point I was making in my comment. Using Invoke() to call a static method won’t give you the expected polymorphic behavior. It will always call the static method on the base class.

By: Dean

Dean — Fri, 18 Dec 2009 15:06:23 +0000

Dutt, there’s a good example on using delegates to call static methods in C# on MSDN. Check out Microsoft’s delegates tutorial: http://msdn.microsoft.com/en-us/library/aa288459%28VS.71%29.aspx

By: nayak

nayak — Wed, 16 Dec 2009 05:03:00 +0000

short & good explanation, but seems it is controdicting the what says in below articles. just sharing the link incase uses feel useful.

Can static methods be called using object/instance in .NET

http://msdotnetsupport.blogspot.com/2009/12/static-methods-calling-using-object-c.html

By: Dutt

Dutt — Tue, 15 Dec 2009 08:43:06 +0000

Thanks for this. very nice one.

can you also please provide a sample on using delegates to static methods using object.

Thanks, Dutt

By: Dean

Dean — Tue, 06 May 2008 01:37:49 +0000

You’re right Simon. (Did I mention I was being lazy?) The main insight I derived from reading all the articles and comments was that the “static” keyword meant more than I thought it did. In C#, “static” means that the compiler must know — at compile time — exactly which method to call. That rules out most polymorphic behavior. It also makes calling static methods from instances problematic. VB.Net doesn’t quibble here, but C# opts for compiler errors.

By: Simon

Simon — Sat, 29 Mar 2008 23:48:19 +0000

Those blog links seem to mainly be about calling statics on generic parameters… (rather than just a standard object instance). Which is indeed annoying, but I’d also say, generally not necessary in a normal design; you’re probably better off using some sort of singleton instance or something.