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
It would be great if we can see where types are defined where the type is not part of the source code. Right now if I can't "go to definition" or "peek definition" - I have no idea where is this type defined.
It would be amazing if we could get the same behaviour as in Visual Studio IDE where it displays a "[from metadata]" tab with the assembly name, namespace and list of members in C# code, but even just knowing which assembly and namespace the type comes from would be a start.
Edit:
I noticed one case where extra information is displayed and that's for field/property declaration's type:
The text was updated successfully, but these errors were encountered:
Thanks for the request @ivanz. Adding the "Metadata as Source" that VS has for symbols not defined in source is definitely something we want to do for VS Code. Dupe of #165.
It would be great if we can see where types are defined where the type is not part of the source code. Right now if I can't "go to definition" or "peek definition" - I have no idea where is this type defined.
It would be amazing if we could get the same behaviour as in Visual Studio IDE where it displays a "[from metadata]" tab with the assembly name, namespace and list of members in C# code, but even just knowing which assembly and namespace the type comes from would be a start.
Edit:
I noticed one case where extra information is displayed and that's for field/property declaration's type:
The text was updated successfully, but these errors were encountered: