Contentfiles pollute the root of the project
See original GitHub issueVisual Studio Version: 2019, seems to happen with all versions I have used so far up to 16.6.1
Summary:
Currently contenfiles seem to just get dumped in the root of the project in the solution explorer:
This is very confusing behavior as its not clear where these files are coming from. In our usecase we use contentfiles to deliver some resource files such as textures in our sample packages for our game engine. We would prefer to not show all these files. I saw you can solve it partially with hacks like these:
<None Update="@(None)">
<Visible>false</Visible>
</None>
But you still end up with empty folders appearing.
Steps to Reproduce:
-
Add a nuget package with contenfiles to the solution (for instance our AdamsLair.Duality.Samples.Tilemaps 4.0.0-alpha2 package)
-
See all the contenfiles appear in the solution explorer
Expected Behavior: Show these files in Dependencies/Packages/Packageid. Alternatively make it possible to hide these files by adding a attribute to the nuspec file and csproj.
Actual Behavior: All contenfiles are visible in the root of the project in the solution explorer
User Impact: Very confusing for users, on top of that these files are editable which they shouldn’t be and this leads to nasty bugs. This was already reported in #2141 though but is still not fixed.
Contentfiles have been around for a while now but the bugs in the tooling don’t seem to get fixed. Whats the holdup? This is not production ready like this. Are there any major blockers to fix this?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:13 (7 by maintainers)
To follow up, the issue where linked folders continue to show after their items have been marked Visible=false, has been fixed in the latest ~16.8 Preview~.
Correction; the fix will be in 16.9 Preview 2 when it releases.