Namespace Imports
ReSharper | Options | Code Editing | Visual Basic | Namespace Imports

This page contains options that affect the way ReSharper optimizes namespace import directives in existing codebase.
ReSharper also allows you to adjust some settings that affect the style of namespace import. You can view and change these settings on the Code Editing | Visual Basic | Syntax Style page of ReSharper options
Remove only unused aliases | |
Keep if the alias name differs from the symbol name | If the Remove only unused aliases checkbox is selected, you can opt to keep non-trivial alias import directives, even though they are redundant. Otherwise, ReSharper removes all redundant import directives. |
Namespaces that should not be removed | ReSharper will not report imports of these namespaces as redundant, and will not remove them while running code cleanup. |
Namespaces that should be always imported | ReSharper will always add imports for these namespaces while running code cleanup. |
Namespaces that should never be removed from fully qualified type names | ReSharper will not report these namespaces in fully qualified type references as redundant, and will not remove them while running code cleanup. |
note
ReSharper's settings are saved in settings layers, which allow you to have different settings for different solutions and to share your settings with your team.