Share
ReportHi All,
I am sharing the below development process in our current MS Dynamics 365 environment. Currently 3 teams are working on a shared solution file and we have few pain points in our development process.
|
As all projects' development is carried out in one single Main branch, the developer must ensure all other developers' changes are excluded during "Export from CRM". |
|
After check-in, all excluded changes from other developers had to be removed and undone from the Visual Studio solution. |
|
"Import to CRM" results in failed import if the solution.xml file is not updated correctly with references which would require working with other developers who had made changes to the file. |
|
Developer had to manually import the latest changes for SIT testing. |
To alleviate the above points, I am planning to propose branching and merge the changes back and forth between the Trunk and branches.
Please give your feedback on whether this proposal will work or else please share a better solution to our existing problems.
Appreciate your comments.
*This post is locked for comments
All responses (
Answers (
83
