Keeps making me browse for assemblies

2 posts, 0 answers
  1. Jim
    Jim avatar
    1 posts
    Member since:
    Mar 2012

    Posted 06 Jun 2012 Link to this post

    Version 2012.1.529.12 SP1

    Keeps asking me to "Please specify x location" where x is any of the following:
    • Assemblies already loaded in JD (e.g. System
    • Assemblies referenced by classes i'm trying to decompile (understandable)
    • Assemblies I can't find anywhere

    They don't 'stick' accross sessions, either. If I take the time to browse to the assemblies it's asking for I can finally get to the code i'm trying to see, but I have to do it all over again if i restart JD.

    This is new for me; i just 'upgraded' from an older version to Version 2012.1.529.12 SP1 and now I'm spending more time tracking down and loading addemblies than I am looking at code.

    Is there an archive somewhere of previous versions? The one I was using before was 2012.1.214.2


  2. Tsviatko Yovtchev
    Tsviatko Yovtchev avatar
    549 posts

    Posted 12 Jun 2012 Link to this post

    Hi Jim,

     I beg your pardon about the delayed response. It's been a bit hectic around here recently.

     I understand your concerns. We'll definitely start saving the assembly search paths so taht you don't have to redo everything on each startup. What you can do now to alleviate that situation is check the "Do the same for all references" box and then click on the "Skip" button when asked to locate an assembly. That will make JustDecompile stop asking about current assembly's references. If you try to decompile something whose correctness depends on these references JustDecompile will make its best guess and it will also mark the ambiguous code in red so that you know what goes on.

    Now, it is fairly weird JustDecompile asks for assemblies that are already loaded. Are you sure the strong name of the loaded assemblies is the same as the strong name of the referenced ones? Another thing that matters is the assembly architecture. The CLR (and JustDecompile for that matter) do make a difference between x86 and x64 assemblies.

    As for the assemblies you can't find anywhere those probably are assemblies that hold some part of the inheritance chain of some type used in the assembly loaded in JustDecompile. More often than not JustDecompile needs to check out the complete inheritance chain of a given type. That might be spred over a number of assemblies that are not directly referred to by the assembly that hodls the type you are interested in.

    Tsviatko Yovtchev
    the Telerik team

    Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>

Back to Top