TFS Reviews

My primary use case is within the organization's work environment, which is mainly focused on Microsoft products and TFS as part of our corporate IT infrastructure.

TFS allows me to handle automated builds and release management quite easily. It is user-friendly with a straightforward drag and drop interface, which makes it easier for me to create builds and release pipelines without needing to program YAML files. This setup is especially beneficial to me compared to GitLab.

TFS has room for improvement as there have been global security issues that many companies, including ours, have experienced. There are glitches, such as runners getting stuck, deployments generating errors, and it's becoming outdated. 

TFS is not as fast, easy to use, or configurable as GitLab, despite moving into the cloud.

TFS has been used before my tenure, so the company has been using it for many years.

Its stability is lacking as we have encountered security leaks and glitches. Runners can get stuck, and deployments sometimes face errors.

I have never been involved with TFS support, however, as a Microsoft product, it might have limited global documentation or support options compared to GitLab.

Negative

We are in the process of switching from TFS to GitLab as TFS lacks the ease of configuration, cloud-based functionality, and security features that GitLab offers.

While I do not know the exact pricing, TFS is likely more expensive than GitLab.

I have used Google Hangouts personally, and as a company, we are considering GitLab.

TFS would benefit from having global tutorials or documentation like GitLab. The security issues should be addressed, and incorporating AI integration like Copilot could be beneficial.

I'd rate the solution six out of ten.

We use TFS for volume control, source checking, and source control.

The most valuable feature of TFS is that it keeps the code secure while working collaboratively in a team of four or five individuals.

We have different teams working on different solutions using different technology sets. At the backend, it has good source control. We work with Microsoft technology stack, open source stack, as well as IBM stack. We have different teams working on the backend with TFS as our source control.

I would like to see TFS improve its web interface as there are some limitations with IDs and the integration behind it and with open-source tools like VS Code.

As a version control, we have found some inconsistencies related to updates from previous versions. If you set up the Git repository, and you want to change it back to TFS, it is a bit confusing now in the latest update. We were hung up when two repositories were intermingled together. We were confused about why the Git project was not converting to TFS. I believe Microsoft is supporting the Git repositories. 

The TFS TFVC is not user-friendly because, for Git repositories that you have already created to use the TFS repositories, you need to go back into the ID to Video Studio when the TFS repository comes up by default.

Using the web interface, by default you get the Git repository. For a team that is not familiar with this and is not using the ID as a video studio or VS, code management gets difficult. Even with VS Code as an open source ID, TFS at the backend as a repository is difficult and integration is complex.

I have been using TFS on a daily basis for five years.

So far, I have found TFS to be stable.

The solution is scalable, however, we do not need to scale because we do not have many people on each team. The administration part requires three or four people, and for development teams, we have about 15 team members who actively use VS Code.

The initial setup of TFS is really just a click. It is basic and not complex.

We deployed the solution in-house.

Our organization has an enterprise license with TFS.

We explored other sources before. We also used some open-source tools.

We are considering trying another solution as we don't find TFS assistance or community help when compared to Git.

TFS is a good solution once you get comfortable using it. If you are coming from TFS 2013 or TFS 2015, you are going to find the 2019 version different. I understand that TFS is moving towards the cloud, so all the features are designed with this in mind. In the 2019 version, you will see more DevOps-related tools and automated app tools.

The solution is easy and complex at the same time. If you are familiar with pipelines, you will find it interesting. You need a technical team to provide help and assistance to get the whole value from 2000 DevOps TFVC. If you are not actually fully exploring the feature set or using them, it is just another source control like any other open-source control.

If you gain experience with the iron value sets with TFVC DevOps, the whole project management will be smooth and stable. Releases will come out but all the hiccups between the teams, such as the development teams, QA teams, and deployment teams will smooth out. 

I would rate this solution an eight out of ten overall.

For customers, we work in banking, finance, and healthcare domains, where there is a huge amount of data from customers and other types of applications and databases. We access this data for automation purposes. Many times, we utilize TFS for this type of thing.

Currently, we are focusing on the security features of TFS, such as the Credential Vault. We use it to store all credentials securely and provide access to specific stakeholders.

TFS should have capabilities similar to Git, like storing all types of artifacts in the repository. It should offer features that allow DevOps teams to track the changes made to the source code or by developers and generate automated reports and dashboards. This would make it easier to monitor and get information without searching through logs manually.

I've worked with TFS for more than three to four years.

Once TFS is installed, there are no major issues. I would rate the stability at seven out of ten.

The scalability is good because TFS is backed by Microsoft, allowing easy integration with other Microsoft applications. It supports a range of capabilities which can be utilized effectively. I would rate the scalability at seven out of ten.

There are some issues with the support team as we need to wait for a long time to get a response. The SLA needs to be improved. Direct communication, such as chat, to showcase screens would help resolve issues faster. I would rate the customer support at five out of ten.

Neutral

The initial setup was somewhat challenging, taking two to three days the first time due to our inexperience. We faced issues such as getting appropriate access and connecting TFS with our current environment. Once we prepared documentation, subsequent setups were easier and quicker, taking only two to three hours.

There are many version control options available in the market. From a costing and licensing perspective, I would rate it around six out of ten. It is not the cheapest product, but it offers good value for money.

I would recommend TFS to anyone planning to use it. It offers valuable features, though they need to be improved over time.

I'd rate the solution six out of ten.

1. SCM functionalities

2. ALM features

3. Build capabilities

4. Deploy options

5. Web portal

6. Release management

7. Support for multiple languages

8. Plug-ins for open source tools, like Sonar and Jenkins

9. Very good, user-friendly UI

10. Test management: capturing/creating defects

11. Reports

12. TFS community, APIs, and support

We have set up a centralized TFS server.

All delivery projects are clients for this TFS.

They are using it for code-repository, ALM, and for DevOps implementation.

1. Customization of build templates - better tools.

2. Tracking

3. More friendly Test Lab setup (in TFS 2013; I didn't verify in TFS 2017).

4. More user-friendly on SharePoint integration (in TFS 2013; I didn't verify in TFS 2017).

We have been using this for more than three years during all development projects. Major SCM and TFS only.

Nope. Installation is very easy. We have set up "Multi-node" installation:

• Application tier
• Build server
• Database server
• Reports server.

No, stability is fine.

We encountered some issues with the report server when the service user password changed. Otherwise, until today, we haven't faced issues in the production environment.

Nope.

Very good.

Very good.

We used VSS and most of our projects are in Microsoft Stack. Opted to choose TFS for incorporating DevOps and easy integration of VS IDE. There are many advantages.

Setup is straightforward. As I mentioned earlier, we did a multi-node installation.

In-house.

Yes.

Not idea on this one as it was done by a different team.

Yes. VSS and Git.

With respect to all the Microsoft Stack development, we use TFS as a repository and source version control system.

TFS is very user-friendly. It is easy to use and has a smaller learning curve.

TFS should allow more integration with different platforms.

I have been using TFS for the past four to five years.

TFS is a stable and robust solution.

TFS is a scalable solution.

I have never used Microsoft’s technical support.

We used SSMS and Visual Studio before, but then we switched to TFS because it is a native product of Microsoft.

The setup was straightforward. It took only five to ten minutes to deploy.

We did it in-house. TFS is user-friendly. So we do not require much help to deploy. An administrator can implement it.

TFS is worth its money.

TFS is not cheap. We pay for monthly licensing at the enterprise level.

I use the 2022 version of TFS. Currently, we are integrating GitHub with Visual Studio. It is a better combination when compared to TFS. So our organization is leveraging it. I haven’t faced any issues with TFS’s performance. GitHub can be used on many different platforms. That is why we shifted from TFS to GitHub for version control.

For data integration projects, to deploy the integration solution, we need to prepare the files based on the specifications. Then it is deployed into the production or any other environment we want to deploy.

My organization has been using TFS for a long time now. From the time I joined the organization, I have been using TFS. Now we use GitHub because Microsoft has acquired GitHub. If required, we can also add more developers to TFS. I’m not a part of the purchasing department, so I do not know the exact price of TFS. I would rate TFS a nine out of ten.

We are developers using the TFS for controlling, and for continuously developing our code.

I am not familiar with all of the features, as I only use it a bit for some of my projects. 

I am using the new kit because it is open source and has many good features.

What I like the most is that you can set permissions on just one folder.

For me, it was easy to use.

There are many things that I cannot do, and I have a lot of bugs. For example, if I want to merge two branches together, sometimes TFS will merge them automatically and I couldn't find the changes and had to check them myself.

That wasn't very good for me and I couldn't understand all of them and wasn't able to interact with them.

The merging could be simplified and improved.

I would like to see more features included for branching so that it copies your source code to the other branch, and have it in a separate folder.

We have been using this solution for five years.

We have not had any issues with stability. It's a stable product.

It's a scalable solution. We have 100 users in our organization.

I found the initial setup straightforward and easy.

We have a team of four or five to maintain this solution.

We are using the open-source version.

I would recommend this solution to others. It's definitely a good product. If you are looking to set up custom privileges then it's a good option for you. It has several features. If you want to secure your code, TFS is a good choice, as it can do it easily.

I would rate TFS a five out of ten.

We use TFS for forecast management.

The tool is sufficient for our business.

We encounter issues with backups.

I have been using the solution for three to four years.

TFS' stability is fine.

I rate the tool's scalability an eight out of ten.

The solution's technical support is very good.

TFS is easy to install. We had a team of two to three persons to handle the deployment.

TFS is a scalable and useful solution. I rate it a seven out of ten.

We use it for code archiving, complete CI/CD functionality, code propagation, code repository, etc.

Team Foundation Server (TFS) is easy to use, and we have a complete trail and traceability. We also like the access control part.

The price could be cheaper.

We're going for a cloud solution that will give us similar functionality and integration with our other products that we are customizing, like SFD. At present, those codes aren't many. 

I've been using it for more than eight years.

It is stable.

It's scalable. We have around 45 users.

We deployed it using an in-house team. You will need two to three people who are in the DevOps teams, who do all the testing, and programmers, who use it and check the code.

You will need to obtain server and account licenses.

TFS is a good product, and I would rate it at eight on a scale from one to ten.