Why can't I add a delegate to my interface?
7 Answers
You can use any of these:
public delegate double CustomerDelegate(int test);
public interface ITest
{
EventHandler<EventArgs> MyHandler{get;set;}
CustomerDelegate HandlerWithCustomDelegate { get; set; }
event EventHandler<EventArgs> MyEvent;
}

- 35,831
- 5
- 65
- 110
-
5Why create CustomerDelegate when you can just use Func
? – Jonathan Allen Mar 05 '09 at 01:28 -
1I know, I was just illustrating that you can use pretty much anything :) – eglasius Mar 05 '09 at 02:31
-
9It gets difficult to understand parameters like Func
. Much more meaningful to have a name for that signature. – diachedelic Dec 04 '12 at 04:07 -
4When working across COM you actually have to use your own delegate as you cannot marshal generic types like Func<>, EventHandler<>, Action<>. – Kyle Dec 06 '13 at 19:01
A Delegate is just another type, so you don't gain anything by putting it inside the interface.
You shouldn't need to create your own delegates. Most of the time you should just use EventHandler, Func, Predicate, or Action.
May I ask what your delegate looks like?

- 68,373
- 70
- 259
- 447
-
2This answer actually also solved my problem that I could never find a nice way to use delegates in the situations where I wanted to use them. I.e. don't use 'm :). – Matthijs Wessels Sep 17 '12 at 10:15
this is a delegate TYPE decalaration...
public delegate returntype MyDelegateType (params)
this cant be declared in an interface as it is a type declaration
however using the type declaration above you CAN use a delegate instance
MyDelegateType MyDelegateInstance ( get; set;)
so delegate instances are OK but delegate type declarations aren't (in an interface)

- 4,253
- 1
- 27
- 29
-
Best answer so far. To the point. I much I love when people goes to the point instead of writing speeches. – DavidGuaita Nov 24 '16 at 23:09
A Delegate is a type which can't be declared in an interface. You might want to either use an event(if appropriate) or declare a delegate outside the interface but in the same namespace.
This link may help- When to Use Delegates Instead of Interfaces

- 31,943
- 7
- 66
- 87
The documentation clearly says that you can define a delegate in an interface:
An interface contains only the signatures of methods, delegates or events.
MSDN: interface (C# Reference)
However, in the remarks on the same page it says that an interface can contain signatures of methods, properties, indexers and events.
If you try to put a delegate in an interface, the compiler says that "interfaces cannot declare types."
The Ecma-334 standard (8.9 Interfaces) agrees with the remarks on that page and the compiler.

- 687,336
- 108
- 737
- 1,005
-
2That looks like an error in MSDN. That should be "the signatures of methods, properties or events", shouldn't it? – configurator Mar 05 '09 at 00:12
As others have mentioned, you can only define delegates outside of the interface.
There is little to nothing wrong w/ using delegates.
Personally I think that Func<int, double>
is less desirable than using delegates:
- You cannot name the arguments, so the argument meaning can be ambiguous
It is old news that Events are not thread safe, thus the following code is not ideal:
if (MyFuncEvent != null) { MyFuncEvent(42, 42.42); }
See: http://kristofverbiest.blogspot.com/2006/08/better-way-to-raise-events.html
The safer code is:
MyFuncEventHandler handler = MyFuncEvent; if (handler != null) { handler(42, 42.42); }
You have to duplicate the signature of the event if you want to save it to a variable (or you could use
var
, which I dislike). If you have lots of arguments then this could get very tedious (again, you could always be lazy and usevar
).Func<int, double, string, object, short, string, object> handler = MyFuncEvent; if (handler != null) { handler(42, 42.42, ...); }
Delegates save you from having to duplicate the signature of the method/event every time you want to assign it to a variable type.

- 3,005
- 2
- 36
- 43
-
1However, note that you _can_ name the arguments at the call site of a lambda function (but only if there are more than two):Action
f = (int i, int j) => { }; /* same as, */ var g = (Action – Glenn Slayden Jun 27 '12 at 21:14)((i, j) => { }); Oddly, you can't use 'var' when using the former syntax (which is when it is least needed).
An interface method can accept a delegate as a parameter, no issues. (Maybe I'm not seeing the problem?) But if the intention is to specify an outbound call in the interface, use an event.
There are so many little details, it's a lot easier to just show some code instead of trying to describe it all in prose. (Sorry, even the code sample is a bit bloated...)
namespace DelegatesAndEvents
{
public class MyEventArgs : EventArgs
{
public string Message { get; set; }
public MyEventArgs(string message) { Message = message; }
}
delegate void TwoWayCallback(string message);
delegate void TwoWayEventHandler(object sender, MyEventArgs eventArgs);
interface ITwoWay
{
void CallThis(TwoWayCallback callback);
void Trigger(string message);
event TwoWayEventHandler TwoWayEvent;
}
class Talkative : ITwoWay
{
public void CallThis(TwoWayCallback callback)
{
callback("Delegate invoked.");
}
public void Trigger(string message)
{
TwoWayEvent.Invoke(this, new MyEventArgs(message));
}
public event TwoWayEventHandler TwoWayEvent;
}
class Program
{
public static void MyCallback(string message)
{
Console.WriteLine(message);
}
public static void OnMyEvent(object sender, MyEventArgs eventArgs)
{
Console.WriteLine(eventArgs.Message);
}
static void Main(string[] args)
{
Talkative talkative = new Talkative();
talkative.CallThis(MyCallback);
talkative.TwoWayEvent += new TwoWayEventHandler(OnMyEvent);
talkative.Trigger("Event fired with this message.");
Console.ReadKey();
}
}
}

- 3,099
- 38
- 34