Managing Telerik .NET references in a Git environment

user_2526818 0
Viewed 287

We've got about two dozen projects, which all use different NuGet-packages and a bunch of Telerik WPF libraries, the latter are usually added by GAC, which on its own does not add a hint path to the csproj-File. (Good)

As soon as we use Telerik's upgrade wizard to simultaneously upgrade the references of all projects, Telerik starts copying the files to a local lib folder next to the bin folder and adds hintpaths, which do not exist on other developers machines AND need to be discarded before pushing to Git every time. (Bad)

BTW: We regularly get the same problem (regarding hintpath) with the Spire NuGet-Package.

Now we came up with some suggestions, which we internally valued differently and therefore did not come to an accord:

  • Keep discarding the chunks containing the hint path
  • Ask Telerik to fix the wizard
  • Check the libraries into Git
  • Add Telerik libraries using their NuGet server
  • Create a Libaries-Path we manage by hand, maybe as a network drive

What's other peoples approach to handling those issues?

telerik git .net c#
3 Answers

I'd go for "Check the libraries into git".

Rationale: when a developer (or CI system) checks out your project from source control, he should be able to build it right away without having to install dependencies like GAC assemblies.

user_12788800

You need to use NuGet for that, it's the easiest and most organized way, you should not have a problem for other developers when you install a new package as long as you are committing package.config file, in this case any one will do a build of the solution visual studio will automatically restore NuGet Package.

Make sure to set your NuGet settings as below image shows:

enter image description here

user_69343290

Don't use the Telerik wizard. Add the Telerik dependencies using NuGet. They have a private NuGet repository. See the tutorial here.

user_10935080
Related