Decompiled code requires missing assembly, how can it be?

3 posts, 0 answers
  1. Joh
    Joh avatar
    4 posts
    Member since:
    Dec 2010

    Posted 28 Feb Link to this post

    I have decompiled a 10 years old application and the decompiled code requires a dll which isn't together with the application.
    I cannot understand how it can be possible, if the application requires it, it shouldn't work without, but actually it works perfectly.
    The only logical explanation would be that the decompilation is wrong, but effectively the dlls are signed, so it cannot be that the decompiled code mistakenly requires another dll.

    The required dll is the Telerik.WinControls.GridView.dll, actually the installed application, as well as the installer, don't have it. The only available dll are:

    • Telerik.WinControls.dll
    • Telerik.WinControls.Docking.dll
    • Telerik.WinControls.UI.dll
    • TelerikCommon.dll

    And effectively from the decompiled code some user controls use the Telerik.WinControls.RadGridView control, and in the application these user controls have a grid, but I cannot really say, if the grid is the Telerik RadGridView control or not. But this is exactly what I cannot explain, either the grid in the user controls isn't the Telerik RadGridView control, so the decompilation code is wrong, otherwise how can it be that the application uses the Telerik RadGridView control without having its dll?

  2. Joh
    Joh avatar
    4 posts
    Member since:
    Dec 2010

    Posted 01 Mar Link to this post

    Where I can find the Telerik.WinControls.GridView.dll version 5.0.3.0?
  3. Alexander
    Admin
    Alexander avatar
    336 posts

    Posted 02 Mar Link to this post

    Hi,

    Here are some possible scenarios:

    1. None of the types from Telerik.WinControls.GridView.dll is used at runtime. All references are loaded into memory on demand, so if the program flow does not hit any usage of class from this library, then it does not try to load it at all.
    2. Telerik.WinControls.GridView.dll is added to the GAC and it is resolved from there.
    3. The app.config file is used to change the probing file path and the assembly is not right next to the application, but in a child directory.

    You can try determine from where the assembly is loaded (or if it is not loaded at all)

    Regards,
    Alexander
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top