You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Quick and easy" is a funny expression. I would say there is a heirachy of ease:
Razor only: Things that have "N" in both Roslyn and Web Tools columns, and therefore have no dependencies outside our repo. Sadly the only two of these left are outside of LSP, so might have other unknown hurdles.
Web Tools only: Things have an "N" in the Roslyn column, but "Y" in Web Tools, means all of the code changes are confined to our repo, since our method of communcation with Web Tools hasn't changed
"Easy" Roslyn: Things have a "Y*" in the Roslyn column, from a cursory look, use only workspace services in Roslyn, so should "just" be a matter of exposing helper methods through our EA, and calling them
Everything else: Things that have a "Y" in the Roslyn column potentially require rework or rearchitecting on the Roslyn side (modulo my understanding of MEF)
Worth noting that 3 and 4 are somewhat blocked on Roslyn LSP types being available to us, too
Display
Not in platform. See AB#2032948Fixed with AB#570071Not in platform. See AB#2032948Fixed with AB#570071. Not supported in VSEdit
No IBraceCompletionServices in OOP?Fixed in dotnet/roslyn#73756Navigate
Needs MetadataAsFileService which needs WorkspaceFixed in dotnet/roslyn#73781Roslyn side isn't in OOPNo idea why I wrote that.Other
MonitorConfigurationFilePathProjectInfoThe text was updated successfully, but these errors were encountered: