Re:The JustDecompile .NET decompiler engine has been open-so...
by exhilaration on Tuesday May 05, 2015 @11:17AM
(#9492941)
How does this compare to dotPeek from JetBrains? https://www.jetbrains.com/decompiler/
[ Parent
| on HN ]
Re:The JustDecompile .NET decompiler engine has been open-so...
by felickz2 on Tuesday May 05, 2015 @11:27AM
(#9493001)
Much better for newer features... for async/await dotpeek would show state machine ( which was actually cool to see), but JustDecompile would actually show me async await in decompiled code.
ALSO, coolest feature is decompile to csproj ... very nice ;)
Re:The JustDecompile .NET decompiler engine has been open-so...
by ttrashh on Tuesday May 05, 2015 @01:28PM
(#9493730)
I had the opposite experience. DotPeek created much better code. using statements were decompiled as usings, JustDecompile produced try/finally blocks.
Re:The JustDecompile .NET decompiler engine has been open-so...
by ChristianGeek on Tuesday May 05, 2015 @11:34AM
(#9493037)
DotPeek has the option to export decompiled code to a project and solution.
Re:The JustDecompile .NET decompiler engine has been open-so...
by skrowl on Tuesday May 05, 2015 @02:41PM
(#9494147)
Agreed. I used it just for the decompile to project.
Re:The JustDecompile .NET decompiler engine has been open-so...
by lawnchair_larry on Tuesday May 05, 2015 @12:08PM
(#9493269)
Sorry I just downvoted you, fat fingered on an ipad. They really need to fix those on mobile.
Anyway, intended to say that in my experience, all 4 major decompilers get tripped up on slightly different things. Between dotpeek, reflector, ilspy, and justdecompile, none could get everything right and I have to take pieces from each to get something buildable again.
Re:The JustDecompile .NET decompiler engine has been open-so...
by LordJZ on Tuesday May 05, 2015 @02:58PM
(#9494249)
It would be so kind of you to create an github issue for things you find ILSpy gets wrong.
https://github.com/icsharpcode/ILSpy/issues