Register assembly to a specific control

4 posts, 1 answers
  1. Adeel
    Adeel avatar
    18 posts
    Member since:
    Sep 2014

    Posted 29 Sep 2014 Link to this post

    I have Telerik Assemblies (old and new) registered in GAC.
    i want that my RadImageEditorControll run with new assemby. How can i do it?

    i want all my application and controlls to run with old assembly only radimageeditor to run with new assembly?
    is there any way to do it in web.config?
  2. Vessy
    Admin
    Vessy avatar
    1389 posts

    Posted 29 Sep 2014 Link to this post

    Hi Adeel,

    Our controls are refered per application, not per single control and there is no way to achiev the described scenario. All of the controls in the application must run one and the same version of the Ui for ASP.NET aJAX suite.

    Regards,
    Vessy
    Telerik
     

    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.

     
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Adeel
    Adeel avatar
    18 posts
    Member since:
    Sep 2014

    Posted 29 Sep 2014 in reply to Vessy Link to this post

    i am using both new assembly and old assembly at a time.
    in web.config i have registered old assembly and only on the page where i have used radimage editor i have explicitly registered New assembly on aspx page and that controll is working fine because it is only in the new assembly but when i place another control on that page then it gives confilict assembly error because that exist in both assemblies .

    i have specified on that page explicitly to run on New assembly so why cant the new control added on that page not working but if i remove it then red image editor control works perfect.
    why cant both controlls runs on new assembly on that page?
  5. Answer
    Vessy
    Admin
    Vessy avatar
    1389 posts

    Posted 02 Oct 2014 Link to this post

    Hi Adeel,

    The experienced behavior is expected since controls are not designed to be used in multiple versions per one project. Even if the controls are registered with different version in the separate pages, they can make requests to a handler form a different version (Telerik.Web.UI.WebResource) which will break their functionality.

    In short - having more than one version of the controls is not supported and highly not recommended scenario which can lead to many unexpected issues.

    Regards,
    Vessy
    Telerik
     

    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