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:
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:
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
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