-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET Core App: It always open reference assembly #1720
Comments
Tried exactly the same like you did with VS 16.3.1 (.NET Core 3.0 final) and it worked correctly with |
What can i do to provide more details? (note also that if ILSpy is not already open, it will open but stay on the previously navigated node -in last usage- instead of the symbol under Visual Studio's caret, it's another problem I have, but not related to the 'reference assembly' issue) |
Ah, sorry, now I see the issue with reference assemblies is occurring here, too. There seems to be an issue with resolving the correct assembly between .NET Core and .NET Framework. |
This issue seems to have come back as of ILSpy/ILSpyAddIn 6.0.0.5836. Following the steps described in the original post results in the same This assembly is marked as 'reference assembly' behavior: In case it helps, the assembly in question shows the following header: // C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Ref\3.1.0\ref\netcoreapp3.1\System.Runtime.Extensions.dll
// System.Runtime.Extensions, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
// Global type: <Module>
// Architecture: AnyCPU (64-bit preferred)
// Runtime: v4.0.30319
// This assembly is signed with a strong name key.
// Hash algorithm: SHA1
// Public key: 002400000480000094000000060200000024000052534131000400000100010007d1fa57c4aed9f0a32e84aa0faefd0de9e8fd6aec8f87fb03766c834c99921eb23be79ad9d5dcc1dd9ad236132102900b723cf980957fc4e177108fc607774f29e8320e92ea05ece4e821c0a5efe8f1645c4c0c93c1ab99285d622caa652c1dfad63d745d6f2de5f17e5eaf0fc4963d261c8a12436518206dc093344d5ad293 |
Please open a new issue |
When writing a .NET Core application, ILSpyAddIn seems to direct to 'reference assemblies' most of the time, which makes it kind of useless because these assemblies don't contain the code of the methods.
Step to reproduce:
var folder = Environment.CurrentDirectory;
CurrentDirectory
> "Open code in ILSpy"ILSpy/ILSpyAddIn 5.0.0.5124
The text was updated successfully, but these errors were encountered: