Unable To Connect To Team Services In Visual Studio For Mac

1. Solved: Hi there, My team uses a GIT Repo hosted at visualstudio.com - is there any way I can connect to it using sourcetree for Mac OS X? Syntax of the config statements and was able to connect to visualstudio.com's GIT server. We recently introduced support for additional hosting services such as GitHub Enterprise,.
2. Stack Exchange network consists of 174 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. Visit Stack Exchange.

1. Unable To Connect To Team Services In Visual Studio For Mac Mac

Visual Studio Team Services supports hosted agents (provided by Microsoft and running Windows) and custom agents that can run Windows, Linux or Mac OS. Any machine you own, physical or virtual, can be a VSTS agent. I choose to create an Ubuntu machine in Microsoft Azure using the docker-machine command line.

Is a great service for developers. Not only do you get a whole Team Foundation Server for free, you also get a place to host your private Git repositories. As long as you use Visual Studio everything works as expected.

However, that changes in the moment you try to use any other client (including ). All you get with those clients is an authentication failure. As it turns out, the single-sign on system you use with Visual Studio Online doesn’t work for Git. If you want to connect you need to create a different set of credentials. If you follow this tutorial, you will be able to use the Git client of your choice without any further problems.

Open in the browser of your choice and log in. You will find your account on the right side of your overview page (don’t mix them up with your personal info at the left side): You are now in the control centre of Visual Studio Online, where you can see all your projects and the documentation. If you click on your name in the top right corner you will find the My profile link: Click on My profile to open your user profile. When you open the credentials tab you should see something like this: All that you now need to do is to click on the Enable alternate credentials link.

The link will disappear and is replaced with a form to set your username and password: When you click on Save changes you should give Microsoft a few minutes to propagate your new credentials through all their systems. From now on you can connect with every Git client to your Visual Studio Online account.

Using Visual Studio for Mac 7.5 and version 0.1.1 of the 'Team Foundation Version Control for TFS and VSTS' extension, I am unable to connect to a on-prem version control after entering my credentials. I suspect this is related to authorization. To reproduce: 1. Enter credentials 2. Click Log In.

A spinner appears and doesn't go away until you cancel. In the background, Wireshark reports an unauthorized response from the server. This also happens in Visual Studio (for Windows), but the windows version retries using NTLM to authenticate. VS for Mac does not.

This is the full extent of the communication between my machine and the TFS server: UPDATE June 15, 2018: A new version of VS for Mac (7.5.2) and the 'Team Foundation Version Control for TFS and VSTS' (0.2.1) extension has been released. To update to it, you may have to manually go to Visual Studio-Extensions-Updates-Refresh. Then install the updated extension and restart Visual Studio for Mac. At this time, it does not install the update or restart automatically.

After updating to the new version, it's still not obvious how to connect to TFS version control systems. This is because it will need a local TFS workspace but if you try to create one on 'Open from Source Control' dialog, it will not work. Instead, use the 'Manage Workspaces' option. I was able to add a new Workspace there once, but it freezed on subsequent attempts. Furthermore, attempting to access the Source Control Explorer results in a spinning beachball of doom also.

UPDATE August 16, 2018: When using Visual Studio for Mac 7.5.4 (build 3) with Team Foundation Version Control for TFS and VSTS extension version 0.3.2, I am now able to create a workspace connected to a on-prem TFS server. During the initial connection, or when using the Version Control-TFS/VSTS-Open From Remote Repository menu, I am able to download source code from the server. However, this download only works when I don't try to download 'too much' at once. It's not clear how much is too much, but I know I can't pull the full project all at once. Unfortunately, Source Control Explorer still seems to be throughly broken. While my server and workspace appear in the appropriate boxes, nothing else does. The main left and right panes are empty and the local path field is blank.

When using Wireshark to capture traffic, it appears that VS might be timing out before the on-prem TFS server can respond with the full TFS server's structure. Specifically, Wireshark shows the following SOAP call with a series of NTLM challenge-responses.POST /tfs/DefaultCollection/VersionControl/v1.0/repository.asmx HTTP/1.1 Accept: text/xml SOAPAction: Content-Type: text/xml; charset=utf-8 Content-Length: 708 Host: tfs.REDACTED.com:8080 Authorization: NTLM REDACTEDBASE64 REDACTEDMACHINENAME REDACTEDUSERNAMEWITHDOMAIN NonDeleted Folder false Once authentication is done, about 56 seconds later the server starts responding with the TFS structure.

After the first 1088 byte TCP fragment is received, Visual Studio responds with a FIN/ACK. Several more segments are then discarded with RST packets sent back to the server. Because of this, I suspect that the Visual Studio extension isn't expecting the server to take so long to prepare a response. To be fair to the server, the extension appears to be asking for a lot of data here.

My TFS project alone is many thousands of files, and we have many TFS projects. I'd wager there are millions of files in the server across them all. Update: September 6, 2018 Despite being marked as fixed by Microsoft, this is not.

In fact, it's worse now than before. After updating to Visual Studio for Mac “7.6.3 (build 1)” and extension 0.4.0 when starting the app, Visual Studio for Mac displays a “A fatal error has occurred” dialog, a “Visual Studio failed to start” dialog, and then closes. The only solution is uninstalling Visual Studio for Mac or manually deleting the folder from /Library/Application Support/VisualStudio/7.0/LocalInstall/Addins/MonoDevelop.VersionControl.TFS.0.4.0. Unfortunately, I can't confirm that this issue was resolved because I can't get far enough to test it. I have tried removing VS and reinstalling both from and from HomeBrew. Neither installation method works for me at this time.

Update: September 7, 2018 Jordan M. From Microsoft got in contact with me and we exchanged logs and a screen capture video I produced showing the issues. Thankfully, it seems that his team was able to diagnose the issue and now extension version 0.4.1 resolved the issue for me. I'm now able to connect to TFS and pull code! Thank you for your feedback! We have fixed this problem in the 0.4.0 preview release of the TFVC extension. Please get the latest version by first updating to VS for Mac 7.6.3 and then using the Visual Studio Extensions.

Updates tab. Note: For new connection issues or other issues with the extension, please help us by reporting them as new problems. This current problem has a lot of great discussion about connectivity issues that are fixed now.

Unable To Connect To Team Services In Visual Studio For Mac Mac

However, some new bug reports are coming in that we want to help troubleshoot more deeply than is possible via comments. Thank you for all the support!