Dynamics 2011 - What should I include in the base solution for the library?

Question

I’m trying to understand the best practices for organizing solutions and, more specifically, what should be included in the “base solution” or “base solution,” library solution. ”

The SDK says the following:

Solution Libraries For an ISV with multiple solutions or a large enterprise deployment, it is expected that many solution components will need to be separated. The best solution methods for sharing components create solution libraries. You create solution libraries by creating an unmanaged solution in a separate organization, and then components into a managed solution. Install a managed solution in another organization and let developers reference these common components from the solutions they create.

Solutions Microsoft Dynamics CRM Framework allows you to create solution layers that are dependent on each other. Typically, you create a solution library that represents the “base” solution. Other solutions can be built on top of this basic solution.

Which components should ideally be placed in a base / library solution? Basic business units and option kits? Key features and workflows?

The documentation for the dynamics does not seem to have a lot of guidance.

Answer 1

If you have any functionality that you plan to use in several organizations that will be reviewed separately from the rest of the organization, I would think about placing this in a separate solution.

, , , CRM-, . , , , , , .

- JavaScript, , , , - -. , - , .

CRM- ISV, . - CRM, , , .