serviceProvider: SVsServiceProvider [](start = 61, length = 35)

This is sort of a layering violation. Is there no other way to implement this without accessing other VS layer services?

AFAIK, no, in the existing implementation (see XmlDocumentation.fs). Can you please explain?

Is the IVsXMLMemberIndexService the only reason for the layer violation? Seems like an abstraction could be added to solve this.

The general idea for these providers is that they are not dependent on VS, so they can work outside of VS, either to run out of proc or be used within a different host.

Yes. We can log a future work item for redesigning this.

Yup. @OmarTawfik and I chatted about that easier. For now, this is VS-only, and we can factor it differently after this goes in.

okay, that was my only hesitation.