South Field blog

In a previous post, I discussed upgrading the Microsoft Dynamics 365 Business Central database to a desired version. In earlier discussions, I highlighted the versatility of Azure DevOps Release Pipelines for various operations. It occurred to me: why not integrate these two operations into a meaningful whole?

It's been almost a month since Business Central 2023 Release Wave 2 became generally available. The past month has been quite busy due to upgrading our existing clients to the latest product version. As always, this process takes up a significant amount of time. You can find a step-by-step guide on the official website outlining the necessary steps for upgrading your database.

Nothing new and revolutionary that doesn't already exist, but here's another way to connect Azure DevOps Release Pipeline and BcContainerHelper.

In the previous post, a slightly more complex way of building an app was described, particularly when dealing with dependencies among apps. Now follows a description of deploying those apps to required environments using Self Hosted agents.

In the previous post, a demonstration was provided on how to construct an application for Microsoft Dynamics 365 Business Central using the Microsoft Hosted Agent.

In the previous post, we described how to create a build pipeline for a simple Microsoft Dynamics 365 Business Central application. In this post, we will demonstrate how artifacts from the build pipeline can be used for deployment to Sandbox and Production environments.

CI/CD (Continuous Integration/Continuous Deployment) is a set of practices and principles used in software development to ensure a streamlined and efficient workflow. It involves the automation of various stages in the software development lifecycle, from code integration and testing (CI) to deployment and delivery (CD).