roslyn
roslyn copied to clipboard
Visual Basic "Move Type to..." refactoring for nested types duplicates entire parent type
This issue has been moved from a ticket on Developer Community.
When I use the "Move type to..." refactoring on any nested type in Visual Basic, a new code file is created for the nested type, and the parent class is declared as partial (as I would expect). However, instead of including only the nested type, the entire parent type is duplicated in the new file. This makes the refactoring effectively useless, since I have to manually remove the duplicated class content in the new file.
Original Comments
Feedback Bot on 11/21/2022, 05:02 PM:
(private comment, text removed)
Feedback Bot on 12/5/2022, 11:33 AM:
(private comment, text removed)
Original Solutions
(no solutions)
Duplicate of https://github.com/dotnet/roslyn/issues/22012