Marko Apfel
Development

ReSharper's 'Arrange Qualifiers' Cleanup Setting, Explained

How ReSharper's Arrange Qualifiers cleanup setting decides when a namespace or type qualifier is redundant versus necessary, with common scenarios and configuration steps.

2 min read

System.Console.WriteLine(...) and Console.WriteLine(...) do exactly the same thing when using System; is in scope — but a codebase where some files use one form and some use the other reads as inconsistent, even though nothing is functionally wrong. ReSharper’s Arrange Qualifiers Code Cleanup setting exists to settle that inconsistency automatically, in both directions.

What it does

Removes redundant qualifiers. When a fully qualified namespace or type reference is unnecessary because a using directive already covers it, the setting simplifies the reference:

// Before
System.Console.WriteLine("Hello");
// After
Console.WriteLine("Hello");  // 'System.' is redundant due to 'using System;'

Adds necessary qualifiers. In the opposite situation — no relevant using directive, or an ambiguous reference where two types share a name across different namespaces — it explicitly qualifies the reference instead of leaving it ambiguous:

// Assuming no `using System;` and `using CustomNamespace;`
Console.WriteLine("Hello");
// After
System.Console.WriteLine("Hello");  // Explicitly qualified for clarity

Standardizes usage across the codebase, so qualifiers show up consistently rather than depending on whichever convention the original author happened to use.

Why it’s worth having on

  • Clarity. In genuinely ambiguous cases, the code explicitly names the type it means.
  • Readability. In the common case, it strips unnecessary verbosity that adds nothing.
  • Consistency. The codebase stops accumulating a mix of qualified and unqualified references based on individual habit.

Where it shows up in practice

  • Stripping System. qualifiers wherever using System; is already present.
  • Adding explicit qualifiers automatically when multiple using directives create genuine ambiguity.
  • Cleaning up legacy code that’s inconsistent about qualifier usage — a common side effect of code accumulated over years and multiple contributors.

Turning it on or off

The setting lives inside a Code Cleanup profile: ReSharper → Options → Code Cleanup → Profiles, select the profile you’re using, click Edit, and toggle Arrange Qualifiers.

The takeaway

Qualifier verbosity is a small thing individually, but it accumulates into real inconsistency across a large codebase — some files terse, some needlessly explicit, with no actual logic behind which is which. Arrange Qualifiers removes the ambiguity in genuinely unclear cases and the noise everywhere else, without requiring anyone to think about it file by file.