Referencing Telerik.Web.UI - Best Practice?

2 posts, 0 answers
  1. Richard Weeks
    Richard Weeks avatar
    95 posts
    Member since:
    Oct 2009

    Posted 01 Dec 2010 Link to this post

    At the moment, we reference Telerik.Web.UI.dll by browsing to the appropriate folder and adding the dll, so in the "Path" property of the Telerik.Web.UI reference Properties in VS we get something like:

    C:\Program Files\Telerik\RadControls for ASP.NET AJAX Q3 
    2010\Bin40\Telerik.Web.UI.dll

    Now, we are using Team Foundation Server 2010 and it goes off and looks for Telerik.Web.UI but TFS is installed on 64-bit so the installation folder the dll will end up in is:

    C:\Program Files (x86)\Telerik\RadControls for ASP.NET AJAX Q3 
    2010\Bin40\Telerik.Web.UI.dll

    Clearly, that's not going to work! My question is, what is the best practice method of referencing the many controls Telerik offer? If the answer can be in the scope of automated builds on TFS 2010, that would be really awesome but I'm interested regardless on what you do.

    (Note: I've read that many developers create a folder in their solution and add / reference the DLLs from there. I reckon that would work but something about it doesn't gel with me. Not sure why, maybe lots of solutions having lots of copies of the DLLs).

    Best,
    Richard
  2. Mira
    Admin
    Mira avatar
    1124 posts

    Posted 06 Dec 2010 Link to this post

    Hello Richard,

    The recommended approach for achieving the desired functionality is to add the Telerik.Web.UI.dll in the Bin folder of the project and to make sure that the reference points to it.
    Alternatively, all the people working on the project could add the dll in the GACs of their machines. You can see how this can be done here.

    I hope this helps.

    Kind regards,
    Mira
    the Telerik team
    Browse the vast support resources we have to jumpstart your development with RadControls for ASP.NET AJAX. See how to integrate our AJAX controls seamlessly in SharePoint 2007/2010 visiting our common SharePoint portal.
  3. UI for ASP.NET Ajax is Ready for VS 2017
Back to Top