Development and deployment process

 


****

All developers for the application work in an individual environment that includes the Visual Studio application. As a reminder, Visual Studio is the integrative development environment (IDE) that is used to develop for Dynamics 365.

****

Deployable packages are created in Visual Studio and then deployed to sandbox, test, and production environments by using Lifecycle Services.

When finishing your code and customizations in Visual Studio, you must make a few considerations. If several developers are on one project, you should perform a Get Latest process to merge all new code that has been checked in by the other developers, and then perform a local build to ensure that your code will not disturb what is in the Azure DevOps repository.

When both processes have been performed, you can check in your code by using Team Explorer, which is connected to Azure DevOps. The code that is checked in will be built in Azure DevOps by using a build pipeline, and this will create a deployable package. Generally, you will not deploy your own code. By using Lifecycle Services, you can apply a deployable package by using the Apply updates tool.


Production deployment

To deploy to production, customers can schedule a downtime that will determine when an update will be applied to the production environment by Microsoft. To schedule downtime to apply updates to the environment, the package must have been applied to at least one sandbox environment in the same project. You can submit a service request for this in Lifecycle Services.

Comments

Popular posts from this blog

How to Create a wizard in x++ d365

how to post trade agreement journals automatically using x++ code

X++ code to CREATE AND POST A TRADE AGREEMENT IN MICROSOFT DYNAMICS 365 in D365 F & O