Sample(s) of C# editor extensibility leveraging Roslyn semantic analysis

[dsaf]

It seems that compiler and editor extensions are separate worlds at the moment:

http://www.visualstudio.com/integrate/explore/explore-vside-vsi

It would be great to have some documentation on how to bridge them.

For example:

1. Basic: extend the C# editor to show a tooltip on class name displaying the full inheritance chain; bonus point: make the chain navigatable.

2. Medium: extend the C# editor to show an adorner on every method call giving details of every exception it might throw; bonus point: make details actionable - generate try-catch blocks.

3. Advanced: create a basic custom DSL with C#-powered intellisense and simple rename refactoring; bonus point: jump-to C# implementation navigation.

Roslyn could be a great boost to extensions gallery not just analyzers. Look at JetBrains - they are reluctant to update their SDK samples, and there are much less extensions for R# then there should be.

PS: 2012/2013 would be great, 2015 is also OK.

[dsaf]

To be more practical: is there any way I can get the whole solution's semantic model in an editor extension? What are the performance implications of doing this in many extensions?

[SLaks]

To answer your specific question:

If you have a TextBuffer, use http://source.roslyn.io/#Microsoft.CodeAnalysis.EditorFeatures.Text/Extensions.cs,66.

If you don't, MEF-import http://source.roslyn.io/#Microsoft.VisualStudio.LanguageServices/Implementation/ProjectSystem/VisualStudioWorkspace.cs,17

[SLaks]

For less-specific information, see http://blog.slaks.net/2014-04-07/exploring-roslyn-part-1-introduction/.
I still need to update this for the more-recent changes (the desktop/portable split, and the fact that everything is now open-source)

[Pilchie]

This is not something the team is likely to work on, however, we'd be happy to incorporate or link to samples others want to write.

[jmarolf]

Issue moved to dotnet/roslyn-sdk #31 via ZenHub