Friday, May 17, 2019

Version Control

Hey r/dotnet!

In a recent one-on-one with my manager, I expressed some concerns about our outdated source control. We're currently running on TFS 2012/2013 (I can't remember which one, I think 2012 though) on-premise, and I personally have ran into some issues with TFS on a couple projects. In more particular, I had a xamarin.forms application that I was working on, and it was a really big pain to get our version control working with VS for mac, and even JetBrains Rider on a mac. I had told my boss about these issues, but I guess it wasn't taken very seriously, as our apps are now in production.

In my one-on-one, I mentioned that I would be willing to do research on options for upgrading our source control software, and everything that goes along with it. I have done some research and understand that TFS is basically no longer a product from Microsoft, and that it's now called Azure DevOps. Devops Services is the cloud-based version, and DevOps Server is the on-premise version. It appears that you have the option of still using TFVC instead of going the git route, but it seems like Microsoft themselves is wanting to phase out the TFVC side, and recommending the git route. I don't have a problem with that, as I think git-based source control is great, and if Microsoft themselves is using it for everything they do (all their github repos) it shouldn't be that hard to convince my manager to switch to it right?

My question to you all is what does your setup for source control look like at your workplaces, and have any of you tackled an upgrade like this before? Really interested to see the responses, and any recommendations that you might be able to provide.

Thanks!

Version Control Click here
  • Blogger Comment
  • Facebook Comment

0 comments:

Post a Comment

The webdev Team