What's the issue with running ILSpy 8.2 with .NET 10?
I cannot make LINQPad work with ILSpy 9. While the command-line parameter issue is easy to fix, there's another problem with their new IPC mechanism. It essentially prevents LINQPad from reliably re-using a particular instance that it created. Will need to log a feature request with ILSpy when I get a chance to get this fixed.
Comments
What's the issue with running ILSpy 8.2 with .NET 10?
I cannot make LINQPad work with ILSpy 9. While the command-line parameter issue is easy to fix, there's another problem with their new IPC mechanism. It essentially prevents LINQPad from reliably re-using a particular instance that it created. Will need to log a feature request with ILSpy when I get a chance to get this fixed.
Try pressing F12 on List on a line like :
List<string> x = new();
Or you can just run directly
"%localappdata%\LINQPad\ILSpy8.2\ILSpy.exe" "C:\Program Files\dotnet\shared\Microsoft.NETCore.App\10.0.0-preview.5.25277.114\System.Collections.dll" /navigateTo:T:System.Collections.Generic.List`1 /separate
The source of the line where It crashes is
https://github.com/icsharpcode/ILSpy/blob/cf4f68bf3a4c7d78209d00f4a354dc0adc4eedcc/ICSharpCode.Decompiler/TypeSystem/DecompilerTypeSystem.cs#L309
as version is just 10.0 rather then 10.0.0
Not sure whether it is this line that is wrong or whether version should not be detected as 10.0 but 10.0.0.
Trying to add some extensions using the new syntax and getting an NRE in LINQPad with no details. Works fine if it's converted to the older syntax.
This should now be fixed with the latest Roslyn update in 9.1.5