-
-
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
Cannot open a DLL produced with .NET 10 Alpha using ILSpy 8.2.0.7535 #3349
Comments
My colleague @ericstj found the root cause: ILSpy/ICSharpCode.Decompiler/Metadata/UniversalAssemblyResolver.cs Lines 196 to 197 in e652490
|
Sorry for the bug, who would've thought that .NET reaches version 10 😉... this is so embarrassing. Thanks for reporting! |
No worries! We caught it early, fortunately. .NET has grown so fast! |
You might consider replacing this parsing with https://learn.microsoft.com/en-us/dotnet/api/system.runtime.versioning.frameworkname?view=net-9.0 or if you keep the parsing, just create a new version if it doesn't have enough parts. That way you don't muck with the string. |
Thank you for the quick fix! |
I created a simple console app that targets .NET 10 alpha (latest available nightly) It compiled without issues. (I shared the csproj and cs code at the end for a repro).
If I try to open the produced assembly, I get an error using this ILSpy version:
Note that the sidebar is able to show the API tree, but if I try to expand a type, I get this callstack:
If I change the language to IL, it shows a bunch of System.Reflection attributes for the assembly:
But a couple seconds later this dialog showed up:
Project code:
The text was updated successfully, but these errors were encountered: