Refactor => Move => Classes to Different project => Doesn't update Project references?
I have been refactoring a lot of code over the past year. I have resharper and love it, however one big thing has been irking me.
My refactoring has involved creating new projects, and moving files from one project to another. This has proven to be a very painful task even when using the Resharper refactor => move method, especially when I am doing this for a larger number of classes.
The problem is in the code that consumes these classes being moved, the project references do not get updated to include the new destination project of the moved classes. This then involves a very very painful amount of time going over each build error and then adding the new references, removing the old using statements etc.
Am I missing something? Does anyone else find this terribly painful? Any reason this hasn't been implemented?
Please sign in to leave a comment.
Hello Andy!
Thank you for the feedback.
This is a known issue, please refer to correspondent YouTrack issue - https://youtrack.jetbrains.com/issue/RSRP-277225.
Please accept our apologies for inconvenience. You are welcome to comment or vote for the issue.
Thank you.