Wrong Telerik .dll being called

2 posts, 0 answers
  1. Lynn
    Lynn avatar
    186 posts
    Member since:
    Sep 2006

    Posted 21 Jul 2013 Link to this post

    I am using VS2012, C#, .Net 4.5, and the just-released version of Telerik controls in a Visual Studio project (.sln).

    Prior to installing the new release today, I was receiving the error shown in the attached screen capture when my code behind file was executing.  I have been converting a VB page to run in C# in this new project and it was running fine (not complete, but compiling clean and executing).  Now all of a sudden, I am receiving the attached error message about being unable to load a previous version of the AJAX controls.

    About that time I received a notification that a new release was available.  I thought this might be a convenient method out of this problem so I downloaded and installed the release, re-opened the Visual Studio 2012 project and ran the Telerik upgrade procedure which ran fine with no errors.  I have included a screen capture of the Telerik library on my hard drive so you can see what it is currently installed.

    I have also included a screen capture of the solution explorer from Visual Studio showing the version number of the referenced Telerik .dll.

    The error message (dll_issue.png) says it is being asked to load 2013.1.220.45.  I have searched this project repeatedly for any reference to this version or to the public key token referenced in the error message to no avail.

    Questions:
    (1) Why is this version being called for?
    (2) What can I do to eliminate this problem?

    I am completely unable to test any code in this solution with this problem.  This project is my highest priority.  Any help would be most appreciated!

    Lynn

  2. Lynn
    Lynn avatar
    186 posts
    Member since:
    Sep 2006

    Posted 21 Jul 2013 Link to this post

    I am closing this item myself.  This was caused by loading a .dll that also utilized the Telerik controls.  It was never compiled with the version of the .dll being called, but nonetheless, once it was compiled with the same version as the primary solution the error went away.

    I am closing it as some kind of assumed visual studio versioning issue.

    I can't seem to be able to mark this as an answer, so please do so for me.  Sorry for erroneously opening this item.
  3. UI for ASP.NET Ajax is Ready for VS 2017
Back to Top