VB.NET转C#：自定义文本框事件无法触发求助

Hey there! Let's dig into that event-triggering issue you're facing while porting your VB.NET custom text box to C#—it’s super common to hit subtle differences between the two languages’ event handling models. Let’s break down the most likely culprits and fixes:

1. Event Declaration & Raising Syntax Mismatch #

VB.NET uses Event and RaiseEvent, but C# has a more explicit delegate-based pattern. If you just translated line-by-line, you might have missed this critical structure:

VB.NET Example (Original): #

Private Event TextChanged As EventHandler
RaiseEvent TextChanged(Me, EventArgs.Empty)

Correct C# Equivalent: #

// Declare the event (usually public or protected)
public event EventHandler TextChanged;

// Create a protected virtual method to trigger the event (standard C# pattern)
protected virtual void OnTextChanged(EventArgs e)
{
    // Use null-conditional operator to avoid null reference errors
    TextChanged?.Invoke(this, e);
}

// Call this method whenever your text box's value changes (e.g., after formatting)
// OnTextChanged(EventArgs.Empty);

This pattern ensures events are raised safely, and lets subclasses override the behavior if needed without breaking event subscriptions.

2. Forgetting to Call Base Class Event Methods #

If your custom text box inherits from TextBox, VB.NET’s Overrides automatically handles base class logic unless you explicitly skip it. In C#, you have to manually call the base method to preserve the native control’s event behavior:

protected override void OnTextChanged(EventArgs e)
{
    // Your custom formatting/validation logic here
    base.OnTextChanged(e); // DO NOT SKIP THIS! It triggers the base TextBox's TextChanged event
}

Omitting base.OnTextChanged(e) will prevent any subscribed handlers from firing, even if you declare your own event.

3. Event Subscription Mistakes #

Double-check how you’re attaching event handlers in C#:

• VB.NET uses AddHandler or declarative Handles clauses
• C# uses the += operator

Example of correct C# subscription:

// In your form's initialization code
MyCustomTextBox ssnTextBox = new MyCustomTextBox();
ssnTextBox.TextChanged += SsnTextBox_TextChanged;

// The handler method
private void SsnTextBox_TextChanged(object sender, EventArgs e)
{
    // Your logic here
}

Also, make sure your subscription code runs after the control is instantiated—if you subscribe before creating the control instance, the handler won’t be attached.

4. Lost Design-Time Event Bindings #

If you’re using the WinForms designer, sometimes migrating from VB.NET can break auto-generated event bindings. Check your form’s .Designer.cs file to ensure lines like this exist:

this.myCustomTextBox1.TextChanged += new System.EventHandler(this.myCustomTextBox1_TextChanged);

If not, re-bind the event via the designer’s properties window or add the line manually.

5. Accidental Event Suppression in Custom Logic #

Review your mode-specific code (date formatting, SSN input) to make sure you’re triggering events after modifying the text. For example, if you’re updating the Text property programmatically, you need to explicitly call OnTextChanged afterward—C# won’t auto-raise events for manual Text updates like VB.NET might in some cases.

If you can share the full, untruncated C# code for your custom control (especially the event declaration and trigger sections), we can pinpoint the exact issue. But these fixes cover 90% of event-failure cases when migrating VB.NET controls to C#.

内容的提问来源于stack exchange，提问作者Kayot