During Solution Explorer search, traces show a lot of allocations related to ProjectTreeFlags:
We use project tree flags in the dependencies node to identify different types of nodes. For attached nodes, we need to obtain these flags for a given IVsHiearchy item. We do this via the VSHPROPID_ProjectTreeCapabilities property.
This innocent property read actually does a bunch of work:
Convert bits and a hash set into a long string of space-separated-values.
Convert this to BSTR
Convert this to a new managed string
If we could instead access the ProjectTreeFlags of CPS's IProjectTree item directly, we could avoid this and allocation marshalling across COM native/managed boundaries.
Reported via email from @ToddGrun and @lifengl.
During Solution Explorer search, traces show a lot of allocations related to
ProjectTreeFlags:We use project tree flags in the dependencies node to identify different types of nodes. For attached nodes, we need to obtain these flags for a given
IVsHiearchyitem. We do this via theVSHPROPID_ProjectTreeCapabilitiesproperty.This innocent property read actually does a bunch of work:
If we could instead access the
ProjectTreeFlagsof CPS'sIProjectTreeitem directly, we could avoid this and allocation marshalling across COM native/managed boundaries.