When converting a WPF form, the Handles command in the code behind file is skipped.

[mjohansson1]

VB.Net input code

    Private Sub TextBoxConnectionString_ValueChanged(sender As System.Object, e As System.Windows.RoutedEventArgs) Handles TextBoxTab3Item.TextChanged, TextBoxTab3Detail.TextChanged
        Changes.Tab3 = True
    End Sub

Erroneous output

        private void TextBoxConnectionString_ValueChanged(object sender, System.Windows.RoutedEventArgs e)
        {
            Changes.Tab3 = true;
        }

Expected output

        private void TextBoxConnectionString_ValueChanged(object sender, System.Windows.RoutedEventArgs e)
        {
            Changes.Tab3 = true;
        }
...
Then, elsewhere in the file:
this.TextBoxTab3Item.TextChanged+= FormEditConfig_Closing;

Details

When converting a WPF form, the Handles command in the code behind file is skipped meaning that no events ever fire.

[mjohansson1]

I checked around and none of the VB->C# converters are doing this. They all just leave it for you to do manually. Manually does not work for me with a million+ lines of code. I just asked ChatGPT to please do this for me and it did. So, workaround is working.

[GrahamTheCoder]

Thanks for the report. There is a whole bunch of code in the converter about dealing with Handles clauses in various different situations. While it'll be hard to perfect the code and I don't have time to take it on right now, you may find that running the converter in debug mode looking at the state around here allows you to tweak things to work for you situation and inform a fuller bugfix:

• https://github.com/icsharpcode/CodeConverter/blob/master/CodeConverter/CSharp/HandledEventsAnalysis.cs
• https://github.com/icsharpcode/CodeConverter/blob/master/CodeConverter/CSharp/HandledEventsAnalyzer.cs