VSIX ships a lot of unrelated files, including Roslyn
It should just reference dlls and allow the roslyn host to load them. Right now, the extension (along with some others) cause my VS to not show quick info. :D
@Therzok ah yeah, something definitely went wrong here 🙂 Initially the addin was based on the LightBulb sample from https://github.com/microsoft/VSSDK-Extensibility-Samples/tree/master/LightBulb (it's pretty out of date)
trying to figure out how to optimize it.
hm.. looks like most of it comes with "Microsoft.CodeAnalysis.EditorFeatures.Text" nuget package which is only needed for GetRelatedDocuments() API
You can most likely ship the vsix without bundling Roslyn, but by having a dependyencu on the .net sdk extension
The assemblies exist in the appdomain, and the host will redirect you to the version it uses. Basically, all the imported packagereference that already exist in VS have to not be locally copied.