The JustDecompile .NET decompiler engine has been open-sourced
1–10 of 20 posts
Re: The JustDecompile .NET decompiler engine has been open-sourced
#2A .NET decompiler written in .NET: I bet "let's try it on itself!" was not an uncommon thought among its users already.
It wasn't this one, but years ago I remember using a decompiler to look through things like the system libraries and the (relatively few) apps written in it at the time, and it was quite interesting how much metadata was available (if it hadn't been obfuscated). I think it's fun and enlightening to take things apart, see how they work, and modify them, so that aspect of .NET really appealed to me, but I still prefer native code for its efficiency and succinctness...
Re: The JustDecompile .NET decompiler engine has been open-sourced
#3A .NET decompiler written in .NET: I bet "let's try it on itself!" was not an uncommon thought among its users already. It wasn't this one, but years ago I remember using a decompiler to look through things like the system libraries and the (relatively few) apps written in it at the time, and it was quite interesting how much metadata was available (if it hadn't been obfuscated). I think it's fun and enlightening to…
the one i was most familiar with was reflector. you could change the languages it was decompiled to from c# to visual basic.
Re: The JustDecompile .NET decompiler engine has been open-sourced
#4How does this compare to dotPeek from JetBrains? https://www.jetbrains.com/decompiler/
Re: The JustDecompile .NET decompiler engine has been open-sourced
#5How does this compare to dotPeek from JetBrains? https://www.jetbrains.com/decompiler/
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-sourced
#6A .NET decompiler written in .NET: I bet "let's try it on itself!" was not an uncommon thought among its users already. It wasn't this one, but years ago I remember using a decompiler to look through things like the system libraries and the (relatively few) apps written in it at the time, and it was quite interesting how much metadata was available (if it hadn't been obfuscated). I think it's fun and enlightening to…
the one i was most familiar with was reflector. you could change the languages it was decompiled to from c# to visual basic.
I'll never forget that morning I started reflector and it deleted itself from my system.
Re: The JustDecompile .NET decompiler engine has been open-sourced
#7http://ilspy.net/ is what I generally use. Functionally modeled after .NET Reflector.
Re: The JustDecompile .NET decompiler engine has been open-sourced
#8How does this compare to dotPeek from JetBrains? https://www.jetbrains.com/decompiler/
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 ;)
DotPeek has the option to export decompiled code to a project and solution.
Re: The JustDecompile .NET decompiler engine has been open-sourced
#9How does this compare to dotPeek from JetBrains? https://www.jetbrains.com/decompiler/
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-sourced
#10This tool helped a lot back then. I would also use DotPeek.