Add support for VB.NET automatic events #2845
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Link to issue(s) this covers:
N/A
Problem
ILSpy did not properly support automatic events generated by the Visual Basic compiler. The backing field naming convention used by the Visual Basic compiler is different than the one used by the C# one. Instead of the field having the same name as the event, it uses the events name and appends the
Event
suffix to it. This different naming convention caused ILSpy to fail to detect automatic events and the decompiled code was very messy.Before:
After:
Original VB code
Solution
I adapted the code for handling automatic events to support the naming convention used by the Visual Basic compiler.
A VBPretty test was added to test this newly added behavior.