adding-solution-explorer-nodes

You add custom nodes by exporting an IAttachedCollectionSourceProvider through MEF, which allows your Visual Studio extension to attach virtual items dynamically under solution or project trees.

IAttachedCollectionSourceProvider is a MEF export contract used to inject virtual collections into the Visual Studio solution tree, enabling extensions to display custom child nodes under solution or project items.

You display virtual items by implementing IAttachedCollectionSource and ITreeDisplayItem, wiring them through an IAttachedCollectionSourceProvider to define root and child node relationships under project nodes.

Yes, creating custom Solution Explorer tree nodes requires in-process APIs from the VSSDK or Visual Studio Toolkit to implement MEF-based attached collection source providers within your extension.

Yes, you support search navigation by implementing ContainedBy relationships and proper parent-child hierarchies, which enables richer search navigation for custom virtual nodes within Solution Explorer.

MEF attached collections require in-process API access via VSSDK or Visual Studio Toolkit, restricting this approach to extensions running inside the Visual Studio process rather than external or out-of-proc tooling.