Sync namespaces for .NET Framework

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

Sync namespaces is only available for .NET Core projects. Please add this functionality to .NET Framework projects, too.

---

Original Comments

Feedback Bot on 4/26/2022, 00:08 AM:

(private comment, text removed)

[sharwell]

💡 This feature does not disable itself based on target framework, but it's only implemented for CPS projects. Projects that still use the legacy project system don't implement the capability support we rely on here:

roslyn/src/VisualStudio/Core/Def/SyncNamespaces/SyncNamespacesCommandHandler.cs

Lines 74 to 75 in 2fd5895

	// Is a project node. Are we C# project node?
	visible = projectHierarchy.IsCapabilityMatch(".NET & CSharp");

[CyrusNajmabadi]

@sharwell should we move this then to the legacy project system owners so they can track these requests?

[sharwell]

@CyrusNajmabadi I don't believe there's any expectation of the legacy project system supporting these features. There are other ways to detect a legacy .NET/C# project, and we can rely on those at the above Roslyn code location.

[janseris]

.NET Framework projects really need this feature. And they need it especially because of the fact that they are the usually the legacy code.
This means that there is monolithic architecture etc. If someone is to fix/refactor/edit/extend an old project, this is one of the essential functionalities together with rich code navigation (number of references etc.).

[sharwell]

.NET Framework projects really need this feature.

.NET Framework projects already have this feature, as long as they are using the new SDK-style projects. The feature is only missing from projects that use the old project system.

With that said, the issue is now marked as help wanted. We would welcome a pull request that updates the line I mentioned to account for the possibility that a project may be using the old project system, provided the feature still works in that case.

[Seabizkit]

please add