New EditorConfig UI Editor doesn't work for external EditorConfig files

[vsfeedback]

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

---

[severity:Other]
After upgrading Visual Studio 2019 to 16.10.0, I tried to use the new . EditorConfig UI editor support and was unable to get it to work initially. After some testing it seems there are 3 use-cases with different results.

1. [Normal] Open a .editorconfig file that is inside your currently open solution
   a. [Result] The file opens with the new editor config UI and populates correctly
2. [Single File] Open a .editorconfig with Visual Studio from file explorer (No solution associated / open in VS)
   a. [Result] The file opens in Visual Studio using a default text editor
   b. [Expectation] The file opens in Visual Studio using the new editor config UI
3. [Drag File] Open any solution in Visual Studio and then drag an external (not in the solution) .editorconfig file into Visual Studio to edit it
   a. [Result] The file opens using the new editor config UI however it fails to populate and just shows an empty editor
   b. [Expectation] The file opens in Visual Studio using the new editor config UI and populates correctly
   c. [Expectation 2] (If Expectation 1 is not possible for some reason) The file opens in Visual Studio using the default text editor

In our current setup we do not have any .editorconfig files directly included or specifically made for a single specific solution. Instead we have a single .editorconfig file placed in a folder above all of our projects and solutions and rely on the built in functionality for .editorconfig files where it will walk up the directory structure to find them. We do this in order to only need to maintain a single .editorconfig file for all of our projects and to help automatically enforce the .editorconfig for anyone who forgets to include one into their new project or solution.

---

Original Comments

Feedback Bot on 6/1/2021, 07:18 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Feedback Bot on 6/2/2021, 09:41 AM:

This issue is currently being investigated. Our team will get back to you if either more information is needed, a workaround is available, or the issue is resolved.

---

Original Solutions

(no solutions)

[Youssef1313]

Related to #53081

[jmarolf]

fixed with #56128

[RPCodeProjects]

This issue is back in VS2022 17.1.4 update. Creates an empty editorconfig file