Our consultant has recommended using TFVC repositories over GIT in Azure DevOps. However, my research indicates that new D365 tenants should ideally use DevOps GIT repositories. Therefore, I have a few specific questions:
-
What is the roadmap for TFVC? Is there any plan for Microsoft to discontinue support for it soon?
-
What is Microsoft’s official stance on using TFVC versus GIT repositories in D365 F&O? Which is the recommended approach?
-
If we start with TFVC, is there an easy transition path to convert to GIT in the future for D365 F&O?
Thanks
Steve
Hi Steve,
I’m not sure of the recommendation of new D365 tenants to use DevOps GIT over TFVC. I haven’t heard of that personally.
-
There hasn’t been any news to discontinue TFVC on any Microsoft platforms concerning Dynamics.
-
From my understanding TFVC has been normally the first option, and I would prefer also to use TFVC as the first option. The introduction of GIT never meant that TFVC would be rendered useless or would be replaced.
-
From the docs I haven’t seen anything related to the support for any transition from TFVC should someone consider to move to GIT.
I hope this answers your quenstions.
1 Like
Hi thanks for responding. I reached out to Microsoft today and they gave me the following answer. Curious as to what others think too. We are just starting out with some implementations across the globe and I know GIT is really the preferred approach in development but I am finding that many in the D365 space use TFVC still. Which I think is fine but for new implementations it seems Microsoft recommends the GIT approach. Still learning this new ERP :))
Hello Steve,
Thank you for reaching out to us.
I apologize for the delay in response as I was working internally to check on your ask.
I am looping my Technical Advisor as well into this email thread. Please refer to the below details:
Although both versions (TFVC and GIT) continue to be supported by Microsoft, however TFVC is considered a finished product and less likely to receive updates compared to Git. It ultimately comes down to the specific needs of teams and project size, where TFVC maintains a centralized code base and efficient in file level permissions it lacks the flexibility GIT provides by being distributed. There are some benefits of using Team Foundation Version Control such as creating and enforcing a uniform workflow of development stages; GIT seems to be a popular choice with developers.
We would recommend using git as
- It Performs better and is widely accepted choice of many
- It can be scaled
- The branching, merging and disposing of feature branches is pretty straightforward
- MS encourages moving existing TFVC to GIT for long term benefits.
Hi Steve,
MS has explained it well with their response. It all comes to the strategy that the teams will define and agree upon. Git is the one which will get future update and support, and TFVC will not get any updates in the future. Also, MS teams working with D365 FO are using Git as of now, so it’s possible. I would recommend reading the following post from Ian Jensen which will give you a brief overview: XPP and Git
TFVC was used for AX 2012 and also F&O documentation originally covered TFVC only. Now Microsoft’s position (as far as I know) is that they leave the choice of a version control system to you. Because many projects use Azure DevOps (there is integration in LCS and such), which supports TFVC and Git, the choice is usually between these two.
There are a few things I would consider:
- As already mentioned, there is no planned investment to TFVC and related tools, which is surely a point for Git. An example of related tools beyond the source control are code review tools (better for Git than for TFVC).
- Branching and merging in Git is (of course!) much more flexible, which gives you new options in comparison with TFVC.
- You need to think about where you’ll store non-F&O code. On my current project, Git is used for non-F&O development (e.g. Azure functions) and TFVC for F&O. Unifying the storage and processes would be beneficial (but it’s not necessary).
- Git is used massively outside F&O. Most (I guess) non-F&O developers are used to Git and want to keep using it.
- On the other hand, F&O developers aren’t usually familiar with Git, therefore training and supervision is needed for some time. If you don’t have anyone experienced with Git, I would recommend hiring someone to help you start.
If I was starting a new project, I would like to use Git. But all my current projects are on TFVC, because that’s how they started and the migration doesn’t look like worth the effort (but it may change later).
1 Like
Hello,
According to info that i got from guys that I consulted with(Finance and Operations Developers), might add some recommendations.
Microsoft still supports TFVC in Azure DevOps. But more and more teams are choosing Git. Right now, there are no plans to stop using TFVC. However, Git is quickly becoming the go-to system for many companies, even those working with Dynamics 365 Finance and Operations.
Git fits better with today’s DevOps practices. It offers continuous integration, pull requests, and easier branching. That’s why Microsoft suggests using Git for D365 F&O. It helps teams work together better and works smoothly with cloud services. Plus, it’s widely used in the industry.
If you start with TFVC, you can switch to Git later. Just know it will take some effort. You’ll need to export your TFVC code to Git and change how branches are organized. There’s a learning curve, especially if your team is used to TFVC. But with the right help from Azure DevOps, you can handle the change. You’ll mainly need to update your pipeline settings and train your team on how to use Git.
In short, TFVC is still around, but Git is the better choice for the future of D365 F&O. Switching from TFVC to Git is doable, but some planning is needed.