I’ve got app 2 solutions (.NET C#) which each share a portable class library (a seperate solution). The app solutions reference the PCL as a project, not by DLL.
What’s the best way to deal with this scenario with source control? The portable class library may change for one version of one of the app solutions but not immediately for the other.
I’m not tied to any source control at the moment, I was attempting to do this with TFS but have workspace issues on the portable class library. I’m open for a better suggestion such as Mercurial or Git!
On way is to keep the shared library in a separate area of the source control system. Each project that depends on the shared library will then have to create a branch of the shared library that’s specific to the project.
Development is isolated on the branch but you can merge changes on the project branch back to the main branch of the shared library. Other projects that already have branches of the shared library can decide if they want to merge changes to the main branch into their own branch.
You will have to perform some merging when the shared library is updated but using this setup you ensure that each project is isolated from changes performed in the other projects. Each project can decide when they want to upgrade to a newer version of the shared library.