NetStandard support

[sirphilliptubell]

Could we get support for netstandard? F12 on a clr type in a project that's using netstandard brings you to the metadata information.

[SLaks]

This is tricky, because VS reports types as they're defined in Reference Assemblies, which does not match the actual source.

There is no way for the extension to bring you to projects like System.Private.CorLib.

See KirillOsenkov/SourceBrowser#106

[Gav-Brown]

Suggested interim solution, change request for Ref12, on KirillOsenkov/SourceBrowser#106 (comment)

[Gav-Brown]

@SLaks As an interim solution, for .NET Standard and .NET Core projects, could Ref12 be altered to open source.dot.net with the search parameter set to the fully qualified method name System.IO.Path.Combine e.g. https://source.dot.net/#q=System.IO.Path.Combine

This isn't as streamlined as opening the source page directly, but is close, and adds more value than the metadata.

[mikernet]

This is desperately needed.

[efreykongcn]

Suggested interim solution, change request for Ref12, on KirillOsenkov/SourceBrowser#106 (comment)

Ref12 with NetCore Support for VS 2017/2019/2022 are available on Visual Studio Marketplace now, searching in the marketplace with keywords Ref12 NetCore Support for VS 2017/2019, and Ref12 2022 for VS 2022.