This isn't a nicely-finished CL app because I only needed to use the code once, but:
- Open your solution in Rider or Visual Studio with ReSharper
- Make sure your solution is checked into version control in case it all goes wrong
- Use the find code issues tool to list unused methods
- If there are more methods than you want to remove by hand, then this is the tool for you.
- Export ReSharper's list of issues as an XML file
- Check out and build this repo
- Mess with ForReal.cs so it points at your code and xml file
- Run the explicit "test" to nuke your unused code
- Try to build your solution, revert any specific edits that broke compilation
There were a few incorrectly removed methods when I tried this on a large codebase, but it still saved a lot of time compared to mashing alt+enter.