All the people that were on my Dynamics 365 Business Central Development courses for Microsoft Italy (and that will be in the next months) already knows that one of the topic that I always I try to emphasize is related to source code management .

Source Code Management (SCM) is a must to have when working with AL (code is now on files and not inside the database as in C/AL) and you absolutely need to have a good SCM system in place inside your organization.

Normally during my courses I provide a practical overview of two systems:

GitHub Azure DevOps

Normally I emphasize the SCM features of these two platforms (GIT support etc) and how you can manage projects and repositories (pull, push, branches etc) directly from Visual Studio Code. Both are great platforms for SCM with GIT. For free , GitHub provides unlimited public repositories but no private repositories, while Azure DevOps gives you unlimited public and private repositories for teams with a maximum of 5 people (over that number you have to pay for users).

When people asks me what I prefer or what I recommend, I’ve no doubts on the answer: Azure DevOps .

I think that for working in teams inside a company (so not only for open source projects), Azure DevOps is much better and it offers many more features that GitHub. The main differences in my opinion is expecially related to project management and testing/pipelines.

I’m not an Azure DevOps guru for sure, but I want to talk here a bit about many interesting Azure DevOps features that you can start using from today for managing your Dynamics 365 Business Central development projects.

To start, first of all you have to open a new project in Azure DevOps, select the project visibility (public or private), the Version Control system (GIT or TFS) and the Work Item Process you want (Agile, Scrum etc):


Using Azure DevOps for managing your Dynamics 365 Business Central projects

When the project is created, you can go to the project page and start to invite your team’s members:


Using Azure DevOps for managing your Dynamics 365 Business Central projects

When the project is created, a GIT repository is created online for you (and from here you can clone it locally etc., I don’t talk about that now).

As a project manager, the first thing you can do is to click on Backlogs and create a backlog for your project (product backlog corresponds to your project plan, the roadmap for what your team plans to deliver). Here you can create phases and tasks and assign that tasks to users:


Using Azure DevOps for managing your Dynamics 365 Business Central projects

On the right side of the Backlog page you have the Sprint panel. With Scrum methodology, teams plan and track work at regular time intervals, referred to as a sprint cadence . You define sprints to correspond to the cadence your team uses. You can select a Sprint, define the starting and ending date and then assign activities from Backlog to a specific Sprint by dragging the activities (here for example I assign the Customer Category Development activity to the Sprint 2):


Using Azure DevOps for managing your Dynamics 365 Business Central projects

After scheduling activities and sprints, you have also other interesting views. If you click on Work Items , you can see the work items status (only work items assigned to you, all work items etc):


Using Azure DevOps for managing your Dynamics 365 Business Central projects

If you click on Boards , you can have a board of your project (view of your project tasks as card ordered by status where you can move tasks by using drag & drop in order to change their status):


Using Azure DevOps for managing your Dynamics 365 Business Central projects

If you select Sprints you can see details of every sprint (iteration path) defined in your project. Here you can have a Taskboard view and you can see the sprint backlog and capacity:


Using Azure DevOps for managing your Dynamics 365 Business Central projects

From here you can monitor the progress of every sprint.

Another interesting feature that I use quite often is what is called the Delivery Plan . Delivery plans display work items as cards along a timeline or calendar view and this is very useful to see expected release dates or delivery dates for your team activities. Delivery Plans are not a standard feature and to have them you need to download and install a Microsoft’s DevOps extension from the marketplace (click on the bag icon on top right corner of your page). The extension is the following (Microsoft, please add it as default in a project workspace):


Using Azure DevOps for managing your Dynamics 365 Business Central projects

When installed, you have a new menu called Plans on the left and by clicking on it you can see your project delivery plan on a timeline:


Using Azure DevOps for managing your Dynamics 365 Business Central projects

The coolest part is that all these project management features are available in a single tool and are totally integrated with the development tools you use every day (alias Visual Studio Code).

Just as a quick example, I can click on Repos and clone the GIT repository to a local folder on my machine:


Using Azure DevOps for managing your Dynamics 365 Business Central projects

You can choose where to create the repository and in few seconds you have a local GIT repository connected to your Azure DevOps repo:


Using Azure DevOps for managing your Dynamics 365 Business Central projects

To use Azure DevOps repositories with Visual Studio Code, you need to install the Azure ReposExtension for Visual Studio Code :


Using Azure DevOps for managing your Dynamics 365 Business Central projects

Yu can connect to your Azure DevOps repository by using the Team:Signin command:


Using Azure DevOps for managing your Dynamics 365 Business Central projects

For authentication, select the following method:


Using Azure DevOps for managing your Dynamics 365 Business Central projects

When connected, you can start work with your AL project. You’re working on a GIT repository, so every time you modify a file the GIT icon in Visual Studio code alerts you that you have some pending changes. When you’re ready to go with your work, you can click on the GIT icon in Visual Studio Code, select the 3 dots icon and then click on Associate Work Items :


Using Azure DevOps for managing your Dynamics 365 Business Central projects

This is not mandatory, but if you work with work items and sprints I recommend to do so because with this feature you can associate your commit to a work item (you can select to the work items assigned to you):


Using Azure DevOps for managing your Dynamics 365 Business Central projects

When the work item is selected, you can commit your changes (file by file or entirely for every modified files) by clicking the Commit icon (you can see the branch you’re working on in the bottom left corner):


Using Azure DevOps for managing your Dynamics 365 Business Central projects

Now you can push the modification to the remote repositoy on Azure DevOps:


Using Azure DevOps for managing your Dynamics 365 Business Central projects
Now, if you go to Azure DevOps and select Repos > Commits

本文系统(windows)相关术语:三级网络技术 计算机三级网络技术 网络技术基础 计算机网络技术

分页:12
转载请注明
本文标题:Using Azure DevOps for managing your Dynamics 365 Business Central projects
本站链接:https://www.codesec.net/view/620835.html


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 系统(windows) | 评论(0) | 阅读(13)