We have a small team and bunch of smaller scale apps that use various Telerik APIs.
What we are currently doing is installing the Telerik dists on our machine via the Control Panel and then using Visual Studio to include those in our projects. The set back to this is we have a certain amount of pain when it comes to matching up each developers installed version of the various Telerik dists and we also have to commit the current version of the Telerik dist that the app is using into our source control.
We currently host our own Nuget feed for delivering our internal APIs and this saves the APIs being committed with each project and solves the pain of people having mismatched versions of the APIs installed on their machines. We were thinking of doing the same with our Telerik releases. When we update a Telerik dist we just update our Nuget package that delivers it and then update it in the project.
We're just posting on here to confirm that this would be the best approach just incase you guys already have something similar on offer. We can't find any of your premium products on Nuget or your premium client side products such as Kendo on Bower.
A speedy response would be very much appreciated.
1 Answer, 1 is accepted
We are sorry for the late reply.
Currently we do not have a public NuGet feed but we are working on this. However the approach you choose (to use our NuGet packages in your local feed) is valid and it is a good way to solve version mismatch problems.
Another approach is to add our assemblies in the solution folder (Add referenced assemblies to solution option). The assemblies will automatically get added to the source control when using Microsoft Team Foundation Server. In this way installation on each developer machine is not required.
Please let us know if further assistance is required.
Regards,
Vesko
Telerik