Recently, Episerver have moved to a bi-weekly release schedule, which is great as you can constantly upgrade. The bad side of this is, if you’re working on a large project with 7+ people, when someone adds a new project, goes to Nuget installed Epi.Core and the version has changed, everyone has to upgrade everything. If you do this accidentally you end up in re-basing and merge hell as everyone is trying to fix the conflicts in your Visual Studio files, which isn’t fun.
To get around this problem, there is a very simple process you can follow that will prevent your project from accidentally being upgraded. Working on a few projects, a lot of people I’ve talked with didn’t realise there was a different process to adding Nuget packages into your newly created project that will solve all your problems. Most people click on the new project and add the packages they want.. don’t do this!
Instead, you need to add packages on a solution level. To do this, right click on the solution and click ‘Manage Nuget packages for the solution’. From the Nuget Package Manager click on Installed packages. On this page you will find a list of packages already installed in your solution.
All you need to do is find the package you want to add into your new project, for this example I will use Episerver.CMS.Core and click the manage button
From here you will see a list of all the projects in your solution with a tick box next to it, if the project uses it. Simply find your newly created project you want to add the dependency to and click it.
That’s it.. if you folow this simple process you’ll never accidentally upgrade your Episerver version. When you start working on projects with a mix of CMS, Commerce, Find, CMO and a few custom field, like Log.4.Net just following this process will really simplify your merging process