project-system
project-system copied to clipboard
dotnet
File Nesting: Investigate file nesting performance impact on non-web projects
File nesting code showed up in some traces when loading large solutions. This issue will track that investigation.
Does this mean that File Nesting won't be available until the next major release of visual studio?
What is the progress on this issue? Has it been corrected for VS 17.1/2022 Preview? @MiYanni @swesonga
This feature is actively being investigated. Currently, enabling it for all projects makes launching VS slower, especially for large solutions. We need a solution for that.
For now, to manually enable file nesting for non-web projects in VS 2022, add this to your .csproj file:
<ItemGroup>
<ProjectCapability Include="ConfigurableFileNesting" />
<ProjectCapability Include="ConfigurableFileNestingFeatureEnabled" />
</ItemGroup>
@drewnoakes can you provide further updates on this? We already had VS 17.3 launching recently and this is still not there, correct?
Custom nesting rules seem to work fine in VS 17.3.2 now, without the need of the ProjectCapability elements.
It must've made it into the latest release(s), but the issues were not updated.
It is indeed now working using the File Nesting button in the solution explorer!
It must've made it into the latest release(s), but the issues were not updated.
Even the MS Docs are not yet updated:
@ocallesp can you please provide confirmation that this was released as production-ready on VS 17.3.2?
This issue is still open. The fix is quite complex since it requires changing Solution Explorer to allow CPS to apply file nesting to only expanded folders.
This issue is still open. The fix is quite complex since it requires changing Solution Explorer to allow CPS to apply file nesting to only expanded folders.
I'm confused now then. Multiple folks are reporting above that nesting is now working without the csproj flags.
Can you elaborate please?
Here's my understanding of this issue.
The custom file nesting feature does have a performance cost. Enough so that we aren't yet able to turn it on by default for all projects.
However, plenty of people want the feature and can accept the (slight) performance hit. We allow turning the feature on via the button in Solution Explorer for those users.
This work item is tracking whether we can improve the performance to the point where we are able to turn the feature on by default for all users.