This is the second post in a series about source code management. If you haven’t already read the beginning of the story you can find it here.
We’d realised that we’d outgrown our system of one-developer-per-customer and ad-hoc communication between teams about ongoing changes to objects. We needed some more structure and somewhere safe to keep previous versions of objects.
Continue Reading james’s Article on their blog
Blog Syndicated with james’s Permission
More About This Author
- 2018.11.29#Dyn365BCAutomatically Creating a CI Pipeline in Azure DevOps with YAML – James Pearson
- 2018.11.12#Dyn365BCIntegration Between Extensions in Dynamics 365 Business Central – James Pearson
- 2018.11.05#Dyn365BCExtensible Enums in Dynamics 365 Business Central – James Pearson
- 2018.10.23#Dyn365BCExtension Settings in Microsoft Dynamics Business Central – James Pearson