In this simple recipe, we barely scratched the surface of solution hierarchies by separating a common library, and the entities dependent on it, into two separate solutions, as highlighted in this diagram:

When deploying the solutions into a new environment, you must deploy the Packt Common solution first, as the Packt solution has a dependency on its components. Subsequently, the Packt solution can be deployed without any refreshes to the Packt Common solution, if not required. Conversely, you can deploy an update to your common library without re-releasing any of the entities.