Tools to modify your code and account for the ripple effects.
Before Rubberduck, the only refactoring-like tool in the VBE was... Find/Replace (Ctrl+H), which treats the code as, essentially, plain text: it does not differenciate two local variables named
foo in two different scopes, and unless you search for whole words only then it will also find parts of identifier names that match, and it will not be able to tell an actual identifier from a string literal.
Rubberduck changes that: when you refactor/rename a variable, only that variable gets renamed, and all its (early-bound) usages get updated. Rubberduck has several refactorings to offer - not just rename, each designed for specific operations that would otherwise be tedious or bug-prone.
This tab lists a number of feature items worth mentioning. To modify this content, an edit must be submitted from the content admin sub-site.
Create properties out of a module variable.
Extract an abstract interface out of the members of a class.
Rewrites the @Folder annotation for all modules under the target foler.
Rewrites the @Folder annotation for a module.
Removes a parameter from a procedure, and the corresponding argument at all call sites.
Renames an identifier, and updates all resolved early-bound references to it in the project.
Changes the order of parameters in a procedure, and updates the corresponding arguments at all call sites.