You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 11, 2020. It is now read-only.
Create any new DNX-based projects (class lib is fine)
In the project create some nested folders, e.g.:
🔢 Class1.cs
🔢 project.json
📁 AAA
📁 BBB
📁 CCC
Rename the AAA folder (e.g. to QQQ)
RESULT:
Solution Explorer looks like:
🔢 Class1.cs
🔢 project.json
📁 QQQ <-- No children visible here!!!
EXPECTED:
Solution Explorer looks like:
🔢 Class1.cs
🔢 project.json
📁 QQQ
📁 BBB
📁 CCC
However, the folders really are there, they're just not visible in Solution Explorer. If you click Show All Files then you can see the folders. And if you then add anything to that folder, the whole tree shows up normally.
The text was updated successfully, but these errors were encountered:
If this issue is still a problem with the RTW release of Visual Studio 2017, please report a new issue using the Report a Problem tool. While you can still use .NET Core and ASP.NET Preview tools with Visual Studio 2015, Visual Studio 2017 is now the officially supported tool for developing .NET Core and ASP.NET Core projects.
By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio's Talk to Us page for more details.
Please use the discussion topic here for feedback and questions on the deprecation of this issue tracker. Thanks!
Using latest RC1 tooling:
AAA
folder (e.g. toQQQ
)RESULT:
Solution Explorer looks like:
EXPECTED:
Solution Explorer looks like:
However, the folders really are there, they're just not visible in Solution Explorer. If you click
Show All Files
then you can see the folders. And if you then add anything to that folder, the whole tree shows up normally.The text was updated successfully, but these errors were encountered: