Roslyn: "Add Using" refactoring should not simplify when using is within namespace block

[AArnott]

Roslyn’s “add using” refactoring adds simplified usings. That is, my block of using statements appear inside my namespace block, and Roslyn is trimming off the prefix that is common between my namespace and the namespace being imported.

I find "simplified" using statements to be quite confusing. I'd like to turn off simplification of using statements. Please make this an option (or the default behavior).

[Pilchie]

Note that this is part of a set of larger style items around usings (e.g. reporting diagnostics for unsorted ones with a quick fix, etc).

[nertim]

Any idea on when this will be available? Our team just upgraded to VS 2015 and would really appreciate the fix for not adding "simplified" namespaces.

[Pilchie]

It's not currently scheduled to a milestone.

[BillHiebert]

Can we raise the priority of this? Having to manually go back and fix every using is incredibly annoying.

[CyrusNajmabadi]

This does not repro for me. We produce the fully qualified name for an import when adding a using: