Our developers are using that effectively on their checkouts no matter what folder or drive they checkout to. The challenge is to get this to work from jenkins.Ģ) For each csproj in the sln the repository path is set and the hint path for each of our dependent packages is restored.ģ) Voila it seems an efficient strategy. Many of our solutions have use of same packages from nuget. Please observe this causes an efficient use nuget resources and our network. We carefully checked this in at a higher level than all of the slns. We have 100's of slns pointing to that same nuget.Config. We use the same nuGet.Config for every sln. This causes the chain of events to occur when each developer opens the Visual Studio 2015 slnġ) the Repository path is set Relative to the Location of the NuGet.Config being used. (Is it a good design?) see the nfig below:Īuto restore of packages is set for each of these. ![]() Our 150 or so Visual studio Solutions share a relative repository path set higher in source tree than every sln and every csproj. The post - Integrate Jenkins with MSBuild and NuGet appeared first on Automate The Planet. If you enjoy my publications, feel free to SUBSCRIBEĪlso, hit these share buttons.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |