Let me suggest the additional topics for documentation

[lsoft]

from my experience, I think it would be cool to highlight the following topics:

1. in-text adornments (adding a controls, borders, etc; additional under-the-hood aspects like a reusing adornment controls)
2. custom codelenses (example; aspects related with out-of-process execution; any ideas how to automate attaching to servicehub of exp-VS - new VSIX?; duplex datafrom from codelens and host-VSIX? streamjsonrpc? etc etc etc a lot of details are not covered at all)

I implemented both features in the different VSIXes, but it was painful :)

Second topic relates with https://github.com/MicrosoftDocs/visualstudio-docs/issues/6509

Thanks you!

[AraHaan]

I would also love if someone can simplify and improve the docs to writing Project System extensions as well.

For example, let's say I made a project type that is sdk style and the .NET SDK can properly load and build it. That then works by using it's own .NET SDK (as a nuget package) and only has a Build and a clean target (cannot and is not meant to be debugged). The user would want to make a custom project system extension to load that project file inside of visual studio like so:

• the custom project system with only Build and Clean targets (no other targets like debug for example)

Currently the docs.microsoft.com docs for stuff like this is not clear, or even worse outdated or just a combination of low quality, outdated and unclear from the perspective of users who have never written VS extensions before and so do not know where to start with extending the Project System inside of Visual Studio.

cc: @madskristensen