Would anyone mind sharing how they manage upgrading the Telerik controls in a team environment? On one particular project we have three developers all working on the same project. When a release of the Silverlight controls comes out from Telerik we have on person assigned with downloading it, compiling it, checking to make sure everything works, resolving any issues introduced, and then checking the code back into the trunk of the project.
Then the other developers need to install the Telerik controls locally on their machines, make sure their reference paths are all correct, and make sure they can compile. As reference paths can be different sometimes (program files/program files (x86), etc.) and there are differences in the developer machines this process can sometimes take an hour or two for each developer--sometimes much more. Sometimes it moves smoothly.
Add on that when we need to take a Telerik internal build to fix a bug, the developers need to copy those dll's locally as well.
Would it be better to keep all the dependent Telerik DLL's in the "lib" folder in the project and use those as the reference point and update from there? Does the developer then need to do an install again and copy over the internal build if needed?
We tried using the "Telerik Upgrade" option from the telerik menu, which gets the latest release code, then adds a ton of hint paths to the proj file. That doesn't seem like the best solution.
Any suggestions on what you are doing and the best way to go about this would be great. I cringe every time I see a new update and realize we have to go through this pain again.
Then the other developers need to install the Telerik controls locally on their machines, make sure their reference paths are all correct, and make sure they can compile. As reference paths can be different sometimes (program files/program files (x86), etc.) and there are differences in the developer machines this process can sometimes take an hour or two for each developer--sometimes much more. Sometimes it moves smoothly.
Add on that when we need to take a Telerik internal build to fix a bug, the developers need to copy those dll's locally as well.
Would it be better to keep all the dependent Telerik DLL's in the "lib" folder in the project and use those as the reference point and update from there? Does the developer then need to do an install again and copy over the internal build if needed?
We tried using the "Telerik Upgrade" option from the telerik menu, which gets the latest release code, then adds a ton of hint paths to the proj file. That doesn't seem like the best solution.
Any suggestions on what you are doing and the best way to go about this would be great. I cringe every time I see a new update and realize we have to go through this pain again.
1 Answer, 1 is accepted
0
Hello Andrew Smith,
Having a folder in your project which hosts the Telerik assemblies seems to be the correct approach. The references should point to that folder. When a new version comes - just replace the assemblies and update the references. The other people would just need to get the latest version and would not have to install the full package locally.
Kind regards,
Veselin Vasilev
the Telerik team
Having a folder in your project which hosts the Telerik assemblies seems to be the correct approach. The references should point to that folder. When a new version comes - just replace the assemblies and update the references. The other people would just need to get the latest version and would not have to install the full package locally.
Kind regards,
Veselin Vasilev
the Telerik team
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 Public Issue Tracking
system and vote to affect the priority of the items