Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Folder with only Visible="False" items still appears in Solution Explorer #5859

Closed
drewnoakes opened this issue Feb 2, 2020 · 11 comments
Closed
Assignees
Labels
Triage-Investigate Reviewed and investigation needed by dev team
Milestone

Comments

@drewnoakes
Copy link
Member

Given folder structure:

myproj.csproj
Folder\Text.txt

Where myproj.csproj contains:

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>netcoreapp3.1</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <None Update="Folder/Text.txt" Visible="False" />
  </ItemGroup>
</Project>

The folder appears in the tree with no children.

image

Setting Visible="False" on the Folder item doesn't work.


Reported in microsoft/VSProjectSystem#162 which pointed to #1233, yet that is closed and seems unrelated as in the example above the hidden file is within the project cone.

@davkean
Copy link
Member

davkean commented Feb 3, 2020

I think this is known. Given we can implicitly determine that a folder only contains "linked" items, I'm sure we could (but haven't determined) detect a folder with only hidden items and hide it.,

@jjmew jjmew assigned jjmew and davkean and unassigned jjmew Feb 3, 2020
@davkean davkean added this to the 16.5 milestone Feb 7, 2020
@jjmew jjmew added the Triage-Investigate Reviewed and investigation needed by dev team label Feb 14, 2020
@jjmew jjmew modified the milestones: 16.5, 16.6 Mar 4, 2020
@jjmew
Copy link
Contributor

jjmew commented Mar 4, 2020

@davkean I am moving this to 16.6. Can you help us route this issue?

@davkean
Copy link
Member

davkean commented Jun 18, 2020

@davkean davkean closed this as completed Jun 18, 2020
@Dean-NC
Copy link

Dean-NC commented Jun 19, 2020

@davkean Is this fixed in 16.6.0, or will it be in 16.7? I'm on 16.6.0 and it's not fixed.

@TechInterMezzo
Copy link

Is it just me or did this problem return in VS 2022?

@alvisespano
Copy link

Is it just me or did this problem return in VS 2022?

Yes it's back. And I haven't been able to find a workaround, either online or trying myself.

@manojdcoder
Copy link

@davkean Issue is back in VS 2022, could this be reopened?

@drewnoakes
Copy link
Member Author

@manojdcoder this issue does not belong to this repo. It was moved to Developer Community so that it could be assigned to another team (not on GitHub). If you're seeing an issue here, could you please open a feedback ticket with detailed steps. If you link it here, I'll ensure it's routed correctly. Thanks.

@cytoph
Copy link

cytoph commented Jan 17, 2025

@manojdcoder Did you open a ticket in the Developer Community? If so could you link it here? Because I have this problem, too, in the current version of Visual Studio and would like to know if there's something to do about it.

@manojdcoder
Copy link

@cytoph No, I did not. I don't even know what it means to open a ticket in Dev Community outside Github.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Triage-Investigate Reviewed and investigation needed by dev team
Projects
None yet
Development

No branches or pull requests

8 participants