Solution segmentation

In this section, we will look at how to segment solutions when you need to have several solutions.

The general recommendation is to have as few solutions as possible, mainly because having several unmanaged solutions sharing the same components will create cross-dependencies, which might be hard to resolve in the future.

Historically, one reason to segment components in different solutions was poor import speed. In that case, it would have been possible to only deploy parts of the implementation by only deploying a subset of solutions. Since Microsoft has increased the import speed tremendously, this isn’t really a valid point any longer.

Import speed

In the last section, we mentioned the configuration to use the improved import speed. I would like to give you an example of how big the improvement has been. For one customer, we use a mono-solution approach (we have two extra solutions for certain components). The solution contains around 450...