Visual Studio For Mac Vsts

Mac

Join GitHub today

Agent version and platform. 2.109.2 MacOS. VSTS type and version. On-Prem TFS TFS 2015 Update 3 (14.102.25423.0 ) What's not working? Visual Studio for Mac is not supported in the current Version.

GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Sign up
  • I'm ready to bet Visual Studio Code and Visual Studio for Mac will never connect to TFVC. Edit: I lost my bet for Visual Studio Code, it can connect to TFVC using the Visual Studio Team Services extension since version 1.116.0 (2017/04/12).
  • Visual Studio is the recommended tool (superseding Xamarin Studio) on both Windows and Mac. However, the VSTS page Build your Xamarin app says to use 'Xamarin'. Presumably that means Xamarin Studio, even though the the 'Install Xamarin' link on the page points to Visual Studio.
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments

commented Nov 23, 2016•
edited

Agent version and platform

2.109.2
MacOS

VSTS type and version

On-Prem TFS
TFS 2015 Update 3 (14.102.25423.0 )

What's not working?

Visual Studio for Mac is not supported in the current Version. The agent checks only for the hard coded path '/Applications/Xamarin Studio.app/Contents/MacOS/mdtool' (https://github.com/Microsoft/vsts-agent/blob/f7e9a7ee42d0c30f0d31d449bb51d95bd6e9e0fb/src/Agent.Listener/Capabilities/NixCapabilitiesProvider.cs#L66) to set the 'Xamarin.iOS' support feature.

Agent and Worker's diag log

There is no relevant log.

Work around

As a work around we set the Xamarin.iOS variable manually in the build agent and changed the mdtool path in the Xamarin iOS Build step to '/Applications/Visual Studio.app/Contents/MacOS/vstool'.

commented Nov 23, 2016

@thomas-goerlich Cool, thanks for report, we haven't try VS for Mac. Do you want to create a PR to fix this? :)

commented Nov 23, 2016

@madhurig FYI

commented Nov 24, 2016

I don't really know how to fix this (i am not that familiar with the TFS infrastructure/build agents).
Since mdtool was renamend to vstool in Visual Studio for Mac i would think i need to copy the builder.Check() command but what if Xamarin Studio and Visual Studio are both installed on the server? Wouldn't there be two entries for Xamarin.iOS in the build agent or one would override the other?

Sorry i am not much of a help here but at least the problem is reported now :-)

commented Nov 28, 2016

@thomas-goerlich : Thank you for reporting the issue. We will address the issue. You can workaround it by adding the Xamarin.iOS capability manually on your build agent from the web UI.

Thanks,
Madhuri

commented Jan 12, 2017

Close as #744 merged

pushed a commit to prebansa/azure-pipelines-agent that referenced this issue Aug 6, 2019
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.

Visual Studio For Mac Connect To Vsts Git

GPG key ID: 4AEE18F83AFDEB23Learn about signing commits

Visual Studio For Mac Tfvc

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment