事件在C#中是實(shí)現(xiàn)觀察者模式的核心機(jī)制。它允許一個對象在不與其他對象緊耦合的情況下通知它們特定動作的發(fā)生。事件本質(zhì)上是對委托的封裝，使類能夠暴露訂閱方式而不賦予調(diào)用控制權(quán)。例如，Button類中的Click事件基于EventHandler委托，當(dāng)按鈕被點(diǎn)擊時，會調(diào)用OnClick方法進(jìn)而觸發(fā)事件。關(guān)鍵點(diǎn)包括：1. 事件只能由聲明它的類調(diào)用；2. 訂閱者可在運(yùn)行時動態(tài)添加或移除處理程序。定義自定義事件時，可創(chuàng)建繼承EventArgs的類和對應(yīng)的委托，如FileWatcher類通過FileChanged事件傳遞文件變化信息。使用事件的最佳實(shí)踐有：3. 訂閱者不再需要更新時應(yīng)取消訂閱以避免內(nèi)存泄漏；4. 優(yōu)先使用EventHandler而非自定義委托；5. 使用null條件運(yùn)算符避免調(diào)用空事件；6. 虛方法支持派生類擴(kuò)展行為；7. 事件本身并非異步，需結(jié)合async/await實(shí)現(xiàn)異步通知。

Events in C# are a core part of the language’s support for the observer pattern. At their heart, they provide a way for one object to notify other objects when something happens—without those objects needing to be tightly coupled. If you’ve ever used buttons in a UI framework like WPF or WinForms, you've already worked with events.

What Exactly Is an Event?

An event is essentially a wrapper around a delegate. It allows a class to expose a way for other code to subscribe to certain actions, without exposing full control over invocation. You can think of it like a subscription list: interested parties can register themselves and get notified when a specific action occurs.

For example:

public class Button
{
    public event EventHandler Click;

    protected virtual void OnClick()
    {
        Click?.Invoke(this, EventArgs.Empty);
    }
}

Here, Click is an event based on the EventHandler delegate. When someone clicks the button, OnClick gets called, which in turn raises the event. Any method that matches the signature of EventHandler can subscribe to this event.

Key points:

• Events can only be invoked from within the class that declares them.
• Subscribers can add ( =) or remove (-=) their handlers at runtime.

How to Define Custom Events

While .NET provides many built-in delegates like EventHandler, sometimes you need your own custom data structure to pass along with the event. This is where defining your own delegate and event args becomes useful.

Let's say you're building a file watcher and want to notify subscribers when a file changes:

1. Define a custom EventArgs class:

   public class FileChangedEventArgs : EventArgs
   {
       public string FileName { get; set; }
       public DateTime ChangeTime { get; set; }
   }

2. Define a matching delegate:

   public delegate void FileChangedEventHandler(object sender, FileChangedEventArgs e);

3. Declare the event in your class:

   public class FileWatcher
   {
       public event FileChangedEventHandler FileChanged;
   
       protected virtual void OnFileChanged(string fileName)
       {
           FileChanged?.Invoke(this, new FileChangedEventArgs
           {
               FileName = fileName,
               ChangeTime = DateTime.Now
           });
       }
   }

   This gives you flexibility to carry rich contextual information when raising the event.

   Best Practices and Common Pitfalls

   Working with events is straightforward, but there are some gotchas:

   • Avoid memory leaks by unsubscribing: If a subscriber doesn’t unsubscribe, the publisher will keep a reference to it, potentially preventing garbage collection. Always remember to use -= when the subscriber no longer needs updates.

   • Use EventHandler<t></t> instead of creating new delegates: Unless you have a very good reason, prefer using the generic EventHandler<t></t> rather than defining your own delegate. It reduces boilerplate and improves consistency.

   • Make sure to check for null before invoking: In older versions of C#, you'd write if (Click != null) Click(...);. In modern C#, you can safely use the null-conditional operator: Click?.Invoke(...). This avoids NullReferenceExceptions if there are no subscribers.

   • Virtual methods for raising events help with inheritance: By making OnClick virtual, derived classes can override behavior without breaking encapsulation.

   Also, don't confuse events with async notifications—they’re not inherently asynchronous. If you need async behavior, wrap the invocation in a task or use async/await.

   ---

   That's how events work under the hood and how to use them effectively. They’re a powerful tool once you understand the mechanics.

   以上是深入了解C＃eventing模型的詳細(xì)內(nèi)容。更多信息請關(guān)注PHP中文網(wǎng)其他相關(guān)文章！