JD crashes when trying to decompile obfuscated code

3 posts, 0 answers
  1. schddc
    schddc avatar
    2 posts
    Member since:
    Feb 2015

    Posted 18 Feb 2015 Link to this post

    My company has recently started to obfuscate our c# dlls. At this time we have been able to automate the obfuscation through the command line with the obfuscator tool we are using. One of the tests we run on the output is to verify the DLLs were obfuscated correctly, currently this has to be done by hand which involves trying to open the assembly in .NET Reflector and Telerik JustDecompile. Opening the assembly in the GUI works well JD doesn't crash and we can see the DLL has been obfuscated. We would like to automate this test but when we run JD through the command line with our obfuscated DLL JD crashes. We would like for it not to crash and return some error that it failed to decompile.
  2. schddc
    schddc avatar
    2 posts
    Member since:
    Feb 2015

    Posted 18 Feb 2015 in reply to schddc Link to this post

    Sorry about the double post. When I posted the first time I received an error from the forum software. If an admin can please delete my other thread that would be great. http://www.telerik.com/forums/jd-crsahes-on-command-line-when-trying-to-decompile-obfuscated-code
  3. DevCraft banner
  4. Tsviatko Yovtchev
    Tsviatko Yovtchev avatar
    391 posts

    Posted 19 Feb 2015 Link to this post


    Rather unfortunately, obfuscated assemblies are really not a supported scenario in JD. It is close to impossible to test for possible crashes against every version of every obfuscator provided that the sole purpose of an ofuscator is to crash tools like JD.

    On a side note you might try some combination of unit tests and UI Automation tests in your scenario.

    Tsviatko Yovtchev

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

Back to Top