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
- 2019.05.21#Dyn365BCWorking with Azure DevOps Pipelines in YAML – James Pearson
- 2019.05.13#Dyn365BCTesting Your Microsoft Dynamics 365 Business Central Tests – James Pearson
- 2019.04.23#Dyn365BCTesting Microsoft Dynamics 365 Business Central from VS Code – James Pearson
- 2019.04.09#Dyn365BCCalling SOAP Services from PowerShell – James Pearson