Dynamics Community Forum Thread Details

Solution.xml different layout in missing dependencies tags causing conflicts in source control.

Hi D365 community,

Having an issue with the Solution.xml file in source control.

We have 2 developers each with own development environment.

That have the same base solution and are creating changes.

Dev A gets their changes into source control first. (We are using SolutionPackager, Azure DevOps and Azure Git)

Dev B then proceeds to get changes into source control but gets conflicts on the solution.xml in the missing dependencies.

The tags in the missing dependencies contain the same information but they are on different lines which is causing conflicts on the file.

Is there any suggestion on how to manage this without manually editing the format of the missing dependencies?

It has been suggested that these can be deleted as they are dynamically created on export, but i question this approach, will they not needed for the packing of the solution so during the import of solution it will check for these dependencies?

We have tested the above and it imports without the missing dependencies and upon export of the solution we can see that its added them missing dependencies back into the solution.xml, are there any consequences to this method to be aware of?

Thanks,

Peter

Quick Links

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics