Navigate to source and .NET Core Follow
Completed
I create fresh .NET Core 2.0 Console project in Visual Studio 2017 on Windows. Then I try to navigate to source (ctrl + click) to `System.Console.WriteLine` method. It fails to find source code with symbol files and decompiles target assembly. Problem is target assembly (from nuget package microsoft.netcore.app\2.0.0\ref\netcoreapp2.0\System.Console.dll) is a stub so it does not contain any implementation (all methods are empty or throw NotImplementedException). Is there any way I can navigate to actual source code with Resharper from Visual Studio (either with symbols or decompilation of assembly with actual implementation)?
Please sign in to leave a comment.
Hello Evgeny!
Thank you for contacting us.
Could you please specify R# version you are using?
Thank you.
I'm using the last version of Resharper (2017.2.2).
Thank you for the reply, Evgeny!
Thanks in advance!
1. The issue is reproduced in newly created solution. To reproduce I just need to create fresh .NET Core 2.0 console project ("new project" > .NET Core > Console App (.NET Core))
2. Default language of my operating system is russian.
3. After creating fresh .NET Core console project - there is default Main method with System.Console.WriteLine statement. When I ctrl+click on this method, I see the following:
As you can see from screenshot, first Resharper tried to load symbols for System.Console from microsoft symbol servers, but failed to do so ("No debugging information found on symbol servers ..."). Then it navigated me to decompiled source code, but it's just a stub - all methods are empty. I understand that target assembly is indeed a stub with empty methods, so I was asking if that's possible to somehow decompile assembly with actual implementation or get required source code by other means (with guidance from symbols).
Hello Evgeny!
Sorry didn't realize what's the problem at once.
Turned out it's the bug, I've filed it here - https://youtrack.jetbrains.com/issue/RSRP-466583
You are welcome to comment or vote for it.
Thank you.
The issue still exists with Rider & .NET Core (at least w/ .NET Core 3.0 preview 8).
Hello Alex,
Could you please specify your Rider version (Help | About or JetBrains Rider | About)?
Hello Alex,
I've reproduced the issue and filed it on our tracker. Thank you for pointing us to it.