The problem stems from the Visual Studio project management specifics. The references of a project are kept in the project file (csproj/vbproj). These are maintained as <Reference> node, having a <HintPath> subnode, which helps Visual Studio identify where the assemblies are.
The automatic RadControls downloads, performed by the Visual Studio Extensions store the assemblies under the user folder to be able to cope with User Account Control. With that, if your user is named UserWork on your work machine and UserHome on your home machine, the places the Telerik assemblies will get downloaded are C:\Users\UserHome\... and C:\Users\UserWork\.... When the problem fixed for one of the machines, it will reappear on the other unless you have the same users on both.
Here is a suggestion of how to handle the third-party references so that you can even add/remove assemblies to the project and they will get added/removed automatically when getting the latest version from another machine (be your home machine, or the machine of your colleague). Please note, it is your responsibility to have the according numbers of the licenses when others of the team modify the code, related to RadControls.
- Set up the solution to have a SolutionFolder (e.g. named ReferencedAssemblies)
- Add a physical folder in the computer (under the physical folder the .sln file exist in), named for example ReferencedAssemblies. Copy the Telerik assemblies used throughout the solution there.
- Add each of the Telerik assemblies to the Solution Folder (using the Add Existing Item context menu in the Solution Explorer). This way the assemblies there get stored under source control.
- All the projects in the solution, needing the Telerik assemblies reference them through the ReferencedAssemblies folder (the csproj file gets relative paths).
- By the time there is a newer RadControls version, change the Telerik assemblies with newer versions following the steps:
= Remove the references to the Telerik assemblies from all the projects in the solution.
= Use TeamExplorer to check all the Telerik assemblies out
= Use Windows Explorer to replace them with their latest versions
= Use the Solution Explorer to re-add the references to the Telerik assemblies to each project having them referenced before
= Fix any breaking changes there might be, rebuild the project to ensure colleagues' code won't get broken and check everything back in to the source control
= Once a colleague gets the latest version from source control, they now use the newer version of the Telerik assemblies too.
Let me know if that helps.
the Telerik team
Register for the Q2 2011 What's New Webinar Week. Mark your calendar for the week starting July 18th and book your seat for a walk through of all the exciting stuff we will ship with the new release!