RaiseCustomEvent
-
"'Raise<ActualName>Event' ... Why do you use such a strange name for an event?" "I follow Microsoft Guidelines. They use such naming. I found it on their website." "If you happen to find that page again, please send me a link." Joseph did not hesitate. He opened Google, entered some search terms, looked at some results. "Here it is: How to: Publish Events that Conform to .NET Framework Guidelines (C# Programming Guide)[^]". And really, that's what Microsoft did in that article:
Microsoft wrote:
public event EventHandler<CustomEventArgs> RaiseCustomEvent;
And then Joseph thought that's how events ought to be named: start with "Raise", add the actual name, then add "Event"... Thank you, Microsoft.
-
"'Raise<ActualName>Event' ... Why do you use such a strange name for an event?" "I follow Microsoft Guidelines. They use such naming. I found it on their website." "If you happen to find that page again, please send me a link." Joseph did not hesitate. He opened Google, entered some search terms, looked at some results. "Here it is: How to: Publish Events that Conform to .NET Framework Guidelines (C# Programming Guide)[^]". And really, that's what Microsoft did in that article:
Microsoft wrote:
public event EventHandler<CustomEventArgs> RaiseCustomEvent;
And then Joseph thought that's how events ought to be named: start with "Raise", add the actual name, then add "Event"... Thank you, Microsoft.
Let's hope he never looks into the .NET source or else he might come up with many more fantastic MS naming "conventions" :laugh:
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
-
"'Raise<ActualName>Event' ... Why do you use such a strange name for an event?" "I follow Microsoft Guidelines. They use such naming. I found it on their website." "If you happen to find that page again, please send me a link." Joseph did not hesitate. He opened Google, entered some search terms, looked at some results. "Here it is: How to: Publish Events that Conform to .NET Framework Guidelines (C# Programming Guide)[^]". And really, that's what Microsoft did in that article:
Microsoft wrote:
public event EventHandler<CustomEventArgs> RaiseCustomEvent;
And then Joseph thought that's how events ought to be named: start with "Raise", add the actual name, then add "Event"... Thank you, Microsoft.
How does he name his classes and methods? Show him this[^].
Wrong is evil and must be defeated. - Jeff Ello
-
How does he name his classes and methods? Show him this[^].
Wrong is evil and must be defeated. - Jeff Ello
Jörgen Andersson wrote:
The one that says Server Error in '/' Application. would it be? Cheers, Peter
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
-
The irony.
Wrong is evil and must be defeated. - Jeff Ello
-
Try without the trailing
.in the URL: Names of Type Members[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
"'Raise<ActualName>Event' ... Why do you use such a strange name for an event?" "I follow Microsoft Guidelines. They use such naming. I found it on their website." "If you happen to find that page again, please send me a link." Joseph did not hesitate. He opened Google, entered some search terms, looked at some results. "Here it is: How to: Publish Events that Conform to .NET Framework Guidelines (C# Programming Guide)[^]". And really, that's what Microsoft did in that article:
Microsoft wrote:
public event EventHandler<CustomEventArgs> RaiseCustomEvent;
And then Joseph thought that's how events ought to be named: start with "Raise", add the actual name, then add "Event"... Thank you, Microsoft.
No, its totally correct - he's defining an event that is raised when a custom event is raised; totally legit ;-)
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
