5 ms·

>We are moving our code to GitHub as well as switching to use git internally But they were using a different tool internally.

• taspeotis 12y ago
  Probably TFS, which Microsoft use quite a bit internally [1]. [1] http://blogs.msdn.com/b/visualstudioalm/archive/2013/08/20/tfs-internal-usage-statistics-1st-half-cy-2013.aspx http://blogs.msdn.com/b/visualstudioalm/archive/2013/08/20/t...
  • josteink 12y ago
    > Probably TFS, which Microsoft use quite a bit internally But seemingly less and less so, especially in the SDK-teams. Which is definitely interesting. If Microsoft's own SDK-developers don't want to use Microsoft's own source-control and ALM-system, but rather prefers Github, what signals does that send? I would sayed mixed at best.
    • chii 12y ago
      it's an open secret that TFS sucks ass. I dont think anything is going to change that attitude - they might as well use something better, and hence the move.
      • RyJones 12y ago
        Not much of a secret. There was open revolt when we were forced to switch in MSN.
      • tracker1 12y ago
        It isn't all bad, just a bit painful to administrate... that said, iirc quite a few devs at MS started using git for local versioning long before TFS added support for git.
    • ethomson 12y ago
      Well, we use GitHub to host our git repositories for open source and public projects. We use TFS to host our git repositories that are private and closed source. GitHub does a great job hosting open source projects. TFS doesn't. I don't think this is a mixed message, we're using the right git hosting service for the job.