We have a use case where we have a parent solution and we customize this parent solution to create derived (child) solutions.
Child solutions may change and get updated independently from the parent solution. However, we would like to ensure that all child solutions derive from the same parent solutions at all times and that updates to the parent solution propagate to the child solutions too.
The theoretical approach we came up with is: 1) moving the parent solution to a new dev environment to create child solutions, 2) using patches whenever a child solution needs to change, 3) copying the dev environment, deleting the patches, importing the updated parent solution and reapplying the patches when a child solution needs to receive parent updates.
Please see the figure below.
Does it make any sense? Would this work in practice?
Would there be a better way to achieve this?
Many thanks for any input, idea, suggestion. We tried to search for similar topics but came up empty.

Report
All responses (
Answers (