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.02.07#Dyn365BCWorking with Version Numbers in Dynamics Business Central / NAV – James Pearson
- 2019.01.31#Dyn365BC5 Things – James Pearson
- 2019.01.16#Dyn365BCRegular Expressions in Visual Studio Code Search – James Pearson
- 2019.01.09#Dyn365BCAn Introduction to Pull Requests in Azure DevOps – James Pearson