Building a solution hierarchy
The introduction of solutions in Dynamics CRM 2011 significantly simplified promoting your configuration and customization from one SDLC environment to another.
Solutions can be used to create hierarchies of dependent solutions, each containing a subset of your components. Separating solutions simplifies deployments by turning large-scale deployments into a collection of smaller deployments.
In Chapter 2, Client-Side Extensions, we created a JavaScript concurrency library that we bundled within the Packt solution. We then hooked the library with the OnLoad event on the contact form. Recognizing that the concurrency library can be leveraged and reused in other entities, or even other implementations, it is wise to separate it into its own solution. The Packt Common solution created in this recipe will house any reusable common libraries or customization to easily transport them between implementations without worrying about any components that are dependent on...
