-->
Developer Community |System Requirements |Compatibility |Distributable Code |Documentation |Blogs |Servicing
Click the button to download the latest version of Visual Studio 2019 for Mac. For information on the system requirements see the see Mac System Requirementsand Mac Platform Targeting and Compatibility guides.
ASP.NET 5 and Visual Studio Code were among the most interesting technologies mentioned. So, I decided to test using and installing these technologies on a Mac OS X system, running Yosemite. Visual Studio 2019 for Mac version 8.7.8 (8.7.8.4) released September 21, 2020. We added support for Xcode 12 and updated the Xamarin SDKs. We added support for setting a Color set as Accent Color in the Info.plist editor. Visual Studio 2019 for Mac version 8.7.7 (8.7.7.10) released September 15, 2020. Go to Mono Downloads page Download the latest Mac OS installer. Note: If you are running El Capitan you will need to install the very latest mono otherwise things will not work correctly.
For instructions on installing and updating Visual Studio 2019 for Mac, see theInstall Visual Studio for Mac guide.
To learn more about other related downloads, see the Downloads page.
What's New in Visual Studio 2019 for Mac
Visual Studio 2019 for Mac Releases
- October 27, 2020 - Visual Studio 2019 for Mac version 8.7.9
- September 21, 2020 - Visual Studio 2019 for Mac version 8.7.8
- September 15, 2020 - Visual Studio 2019 for Mac version 8.7.7
- September 10, 2020 - Visual Studio 2019 for Mac version 8.7.6
- September 08, 2020 - Visual Studio 2019 for Mac version 8.7.5
- August 25, 2020 - Visual Studio 2019 for Mac version 8.7.4
- August 18, 2020 - Visual Studio 2019 for Mac version 8.7.3
- August 13, 2020 - Visual Studio 2019 for Mac version 8.7.2
- August 11, 2020 - Visual Studio 2019 for Mac version 8.7.1
- August 5, 2020 - Visual Studio 2019 for Mac version 8.7
Visual Studio 2019 for Mac Blog Posts
The Visual Studio Blog is the official source of product insight from the Visual Studio Engineering Team. You can find in-depth information about the Visual Studio 2019 for Mac releases in the following posts:
Release Highlights
- We added support for adding new Open API & gRPC service references to .NET Core projects.
- We added support for right-clicking to run unit tests.
- The Visual Studio Tools for Unity includes three new diagnostics and support for persistent solution folders when Unity is regenerating solution and projects.
- We resolved a significant number of existing bugs and user-reported issues throughout the IDE. Please continue to share your feedback with us using the Developer Community portal.
- Visual Studio for Mac 8.7 supports running on the macOS Big Sur developer preview. If you're already on Big Sur and can't use the updater, visit the Visual Studio for Mac website and download the installer.
Known Issues
Refer to the Known Issues section.
Feedback and Suggestions
We would love to hear from you! You can report a problem through the Report a Problem option in Visual Studio for Mac IDE.You can track your feedback, including suggestions, in the Developer Community portal.
Release Notes
Visual Studio 2019 for Mac version 8.7.9 (8.7.9.9)
released October 27, 2020
Web and Azure
- We updated .NET Core to 3.1.403 and 2.1.811.
Xamarin
- We added support for Xcode 12.1.
Visual Studio 2019 for Mac version 8.7.8 (8.7.8.4)
released September 21, 2020
Xamarin
- We added support for Xcode 12 and updated the Xamarin SDKs.
- We added support for setting a Color set as Accent Color in the Info.plist editor.
Visual Studio 2019 for Mac version 8.7.7 (8.7.7.10)
released September 15, 2020
IDE Platform
- We fixed an issue where Visual Studio for Mac could not be launched and required a full reboot.
Project System
- We fixed an issue with ProjectGuid being removed from project files.
Web and Azure
- We fixed an issue where Scaffolding failed for ASP.NET Core 2.1 Web Applications.
Visual Studio 2019 for Mac version 8.7.6 (8.7.6.2)
released September 08, 2020
Web and Azure
- We updated the .NET Core SDK (3.1.402 SDK and 2.1.22 runtime).
Visual Studio 2019 for Mac version 8.7.5 (8.7.5.19)
released September 08, 2020
Project System
- We fixed an issue where an Uno solution could not be loaded.
Shell and Tools
- We improved performance and reliability.
Web and Azure
- We fixed an issue where initial templates were missing when creating a new Azure Functions project.
Xamarin
- We fixed many unneeded/unwanted popups when working with storyboards in Xcode Designer.
- We fixed an issue with generation of outlets
- We fixed an issue where Visual Studio and Xcode sync keeps updating the Register attribute.
- We fixed an index out of range error in Hot Reload
- We fixed an issue where opening a Storyboard with Xcode Interface Builder was failing.
Visual Studio 2019 for Mac version 8.7.4 (8.7.4.38)
released August 25, 2020
Shell and Tools
- We fixed an issue causing illogical focus order in the Report a Problem dialog.
- We fixed an issue preventing VoiceOver and screen readers from being able to activate links in the Manage NuGet Packages dialog.
- We fixed an issue where large solutions would fail to restore with older .NET Core SDKs installed.
- We increased the color contrast of the selected account in the account dialog.
Web and Azure
- We fixed an issue where a new launch profile added to launchSettings.json was not shown in the project options dialog.
- We fixed an issue where cancelling changes in the project options dialog would not undo run configuration changes.
- We fixed an issue where the OpenAPI / gRPC configuration dialogs were not modal.
- We fixed an issue where the OpenAPI service reference dialog would re-open after the reference was added.
- We fixed an issue preventing ASP.NET Core projects from running in the integrated terminal despite being set to do so in the run configuration settings.
- We fixed an issue where the default run configuration shows the project name twice in main toolbar.
Xamarin
- We improved overall stability
Visual Studio 2019 for Mac version 8.7.3 (8.7.3.13)
released August 18, 2020
Shell and Tools
- We fixed an issue where the properties pad was not updated correctly after changing properties in the solution pad.
- We fixed an issue where open with hex editor opens file with VS Code and not in the hex editor.
Xamarin
- We improved overall stability
- We fixed an issue with debugging an Android app with Xamarin.Android SDK 11.0.0.3
Visual Studio 2019 for Mac version 8.7.2 (8.7.2.4)
released August 13, 2020
Web and Azure
- We updated the .NET Core SDK (3.1.401 SDK and 2.1.21 runtime).
Visual Studio 2019 for Mac version 8.7.1 (8.7.1.15)
released August 11, 2020
Bug Fixes in 8.7.1
Shell and Tools
- We fixed an issue with incorrect dependency folder information with .NET Core 3.1.400.
- We fixed an issue where several UI elements in the properties dialog do not have names for VoiceOver users.
Unity
- We fixed an issue where opening from Unity shows 'Loading...' until quitting and reopening.
Version Control
- We fixed an issue that could result in a
doesn't point at a valid Git repository or workdir.
error message when working with Git.
Xamarin
- We fixed an issue preventing Xamarin developers on macOS Big Sur from compiling and running their projects.
Visual Studio 2019 for Mac version 8.7 (8.7.0.2037)
released August 5, 2020
Note
This release of Visual Studio for Mac now supports running on the macOS Big Sur developer beta builds. If you're already on Big Sur and can't use the updater, visit the Visual Studio for Mac website and download the installer.
New Features
Open API and gRPC Client Generation
Visual Studio for Mac now includes support for generating an API client from an OpenAPI or gRPC service. This includes the ability to generate the client from a local file or URL, manage service references, and regenerate the client code if the service changes.
To add add a new reference to an OpenAPI or gRPC service, right-click on the Connected Services node in the Solution pad and select Open Service Gallery.
After opening the Connected Services Gallery, you have the option to add either an OpenAPI or gRPC reference.
Clicking on either of the options launches a prompt which allows you to enter the service reference, either by file path or URL.
When generating a gRPC client, you can also select whether to generate the following client class types:
- Client
- Server
- Client and Server
- Messages Only (used to generate strongly typed classes based on message properties, with no generated server or client code)
When generating an OpenAPI client, you can specify the namespace and additional options which are passed through to the code generator.
Code generation is based on the dotnet-grpc
and dotnet-openapi
command-line tools.
After generating a service reference, you can view and modify it in the Connected Services Gallery as shown below.
For more information on using a generated OpenAPI client, see the Getting Started with NSwag tutorial.
For more information on using a generated gRPC client, see the Create a gRPC client and server in ASP.NET Core tutorial.
Right-Click to Run Unit Tests
When editing C# classes containing unit tests, developers can now right-click within the body of a test class or method to access options for running and debugging tests.
In addition to right-clicking in the editor, these new commands can be run using keboard shortcuts. If you're using the Visual Studio for Mac key bindings, the commands are as follows:
- Run Test(s):
⌘T
- Debug Tests(s):
⌘⌥T
See Default keyboard shortcuts in Visual Studio for Mac for more information on changing your keyboard shortcuts and The Visual Studio Blog for more in-depth information on this new unit test feature.
Visual Studio Tools for Unity
- We added support to persist solution folders when Unity is regenerating solution and projects.
- We added the following diagnostics:
UNT0015
: Detect incorrect method signature with InitializeOnLoadMethod
or RuntimeInitializeOnLoadMethod
attribute.UNT0016
: Using Invoke
, InvokeRepeating
, StartCoroutine
or StopCoroutine
with a first argument being a string literal is not type safe.UNT0017
: SetPixels
invocation is slow.
Bug Fixes
Debugger
- We fixed an issue where Debugger step operations cause Visual Studio to hang.
- We introduced new logic for calculating width and placement of items in debugger pads.
- We fixed an issue that prevented name/value cells from going into edit mode unless clicking exactly on text.
- We increased the speed of expanding tooltips
- We fixed an issue that created breakpoints in the breakpoint pad when users clicked an empty line in the editor margin.
- We fixed an issue that prevented users from dismissing crash messages.
- We fixed an issue where tooltip behaviour makes it difficult to work.
- We fixed an issue that may have caused UI hang while stepping.
- We fixed an issue where Exception page stays after debugging ends.
- We fixed an issue where the breakpoint pad could become out of sync with line numbers in the text editor display when adding or removing lines of code.
- We fixed an issue that may cause the debugger to break on the wrong statement.
- We fixed an issue that sometimes caused tooltips to remain visible after finishing debugging.
- We fixed an issue where the tooltip may display an array length for a non-array object.
- We fixed an issue that caused a StackTracePad.UpdateAsync null reference error to be written to the logs.
- We fixed an issue that caused erroneous newlines in tooltip values.
Project System
- We fixed an issue where Files in a symbolically linked folder are not built on change.
- We fixed an issue where Adding a new file/asset causes 'Saving...' to take for over a minute.
- We fixed an issue where the Saving message shown forever and unable to continue.
- We fixed an issue with Key bindings for running, debugging and selecting a unit test at caret not working.
- We fixed an issue where clicking the run button may ask you to build again even if the project had just been compiled.
- We fixed an issue where Multi-target order is not correct.
- We fixed an issue where a user Can't close the project.
Testing
- We fixed an issue where Unit tests duplicated namespaces.
- We fixed an issue causing some unit tests not to load.
- We fixed an issue that caused xUnit tests to show full namespaces instead of method names.
- We fixed an issue where The test nodes in the unit test pads are incorrect.
- We fixed an issue with the Unit Test panel not properly grouping tests by namespace when using NUnit TestCase of int. MaxValue.
- We fixed an issue where the VSMac test explorer broken.
- We fixed brought support for unit test markers back to the editor.
Shell and Tools
- We updated NuGet to 5.7 RTM.
- We fixed an issue with keyboard focus inside the property pad.
- We fixed an issue where Visual Studio was crashing on macOS Big Sur. If you have already upgraded macOS to Big Sur and are not able to run VS for Mac, please download the latest installer from https://visualstudio.microsoft.com/vs/mac/ to install the latest stable version and then install this preview from the Preview channel.
- We made fixes to address a handful of stability and performance issues.
- We added a missing key binding for moving through open files (tabs) when using the VS Code key binding scheme.
- We fixed an issue where the start window could be reentered during project creation, making all commands unusable.
- We fixed an issue with broken commands in the start window.
- We fixed an issue where mstest tests were not discovered in Visual Studio for Mac when using Directory.Build.props.
- We have improved how a conflicting key is shown in preferences.
- We fixed several accessibility issues.
- We fixed toggle/undo comments command binding in the Mixed keybinding scheme.
- We fixed an issue where the sorting buttons in the Document Outline pad reset when switching focus between source files.
- We fixed an issue where Control+Tab switching between files gets stuck.
- Png files now open with the Previewer by default instead of the hex editor.
- We improved the way file paths are shown in global search.
- We fixed an issue where showing declaration of some classes causes many assembly files to be shown.
- When adding a new folder to the solution pad, it will now be expanded by default.
- We fixed an issue preventing the mapping of a command to ⌃ (Tab) in keybindings preferences.
- We fixed an issue where a solution is no longer available in the recently used projects list if the .sln file was opened in editor.
- We fixed an issue where Nuget Ordering Beta/Alpha was incorrect.
Source Code Editing
- We fixed an issue where typing was very slow when many files were open.
- We fixed an issue where The 'Document Outline' view does not update at all—for regions and functions.
- We fixed an issue where the Document Outline shows wrong hierarchy when #region is present.
- We fixed an issue where Rename file to refactor causes Visual Studio to Freeze.
- We fixed an issue Trying to open a CSS file in Visual Studio for Mac freezes.
- We fixed an issue where the Document Outline pad for C# never reflects the last editing change.
- We fixed an issue in the C# editor where IntelliSense never displays documentation for current param at call site.
- We fixed an issue where Renaming a variable duplicates the last two characters.
Tools for Unity
- We fixed a bug where breakpoints would not be hit if they were set while already debugging.
- We fixed an issue where checking equality of Enum values didn't return the correct result (Watches, Immediate, Conditonal Breakpoints).
- We fixed
USP0004
, USP0006
and USP0007
suppressors with the following rules: suppress IDE0044
(readonly), IDE0051
(unused), CS0649
(never assigned) for all fields decorated with SerializeField attribute. Suppress CS0649
(never assigned) for public fields of all types extending Unity.Object
. - We fixed generic type parameter checking for
UNT0014
. - We fixed an issue that caused selected Unity Messages to be unchecked after searching in the Add Unity Messages dialog.
Version Control
- We fixed an issue with version control tabs not showing up.
- We fixed an issue where cloning using SSH failed with an error.
- We fixed an issue where the version control system breaks when the .git folder is deleted.
- We fixed an issue where it was not possible to access remote repos over SSH in VS Comm.
- We fixed an issue causing a hang when using version control.
- We fixed an issue where pushing when remote contains changes that don't exist locally takes a long time eventually aborting with errors.
Web and Azure
Net Mono For Mac Os
- We updated the .NET Core SDK (3.1.302 SDK and 2.1.20 runtime).
- We fixed an issue with Entity Framework (CRUD) Scaffolding, where the style of the web page was not loading properly.
- We fixed an issue where Scaffolding failed for a .NET Core 5 Web Application.
- We fixed an issue where a subscription could not be found when trying to publish.
- We fixed an issue with not being able to build React.js and Redux projects.
- We fixed an issue with not being able to open generated code of a service reference.
- We fixed an issue where building Angular projects failed to find clang++.
- We fixed an issue where creating Blazor Web Assembly App projects failed with an error.
- We fixed an issue with unresponsive Add gRPC Service Reference dialogs.
- We added support for adding new Open AI & gRPC service references to .NET Core projects.
- We fixed an issue causing Cannot load solution on VisualStudio for Mac.
- We fixed an issue where the launchsettings.json file is rewritten when loading.
- We fixed an issue where changing the Web App run config does not save to the launchsettings.json.
- We fixed an issue preventing the addition of new run configurations to ASP.NET Core apps.
- We fixed an issue where IntelliSense would erroneously underline valid code in .razor files under certain conditions.
- We fixed an issue where an 'api controller with entity framework' scaffold generates 'MVC controller with entity framework'.
Xamarin
- Support for Xcode 11.5 and 11.6.
- We updated the Xamarin.Forms templates to use 4.6.0 SR 5.
- We fixed an issue that caused reliability issues in the remote build host.
- We fixed an issue where a context menu action was not localized in the Android designer.
- We fixed a handful of crashes reported by users.
- We fixed a few instances where VoiceOver would read labels of elements on Wizard template pages twice.
- We fixed an issue where storyboard resource tags are removed.
- We fixed an issue where Visual Studio for Mac was not generating view controller files for storyboards.
- We fixed some Storyboard errors with Xamarin.mac.
- We fixed an issue where color contrast was too low for the expand/collapse button in the Apple Developer account dialog.
Known Issues
The following is a list of all existing known issues in Visual Studio 2019 for Mac version 8.7:
- In rare cases, it's possible to be up to date with everything but the .NET Core 3.1.300 SDK. If you enter into this configuration and update to .NET Core 3.1.300 using the updater, the notification to update the .NET Core SDK will not disappear until the IDE is restarted.
Top of Page-->
This guide describes how to use Pair to Mac to connect Visual Studio 2019to a Mac build host. The same instructions apply to Visual Studio 2017.
Overview
Building native iOS applications requires access to Apple's build tools,which only run on a Mac. Because of this, Visual Studio 2019 must connect toa network-accessible Mac to build Xamarin.iOS applications.
Visual Studio 2019's Pair to Mac feature discovers, connects to,authenticates with, and remembers Mac build hosts so that Windows-basediOS developers can work productively.
Net Monitor Mac
Pair to Mac enables the following development workflow:
Developers can write Xamarin.iOS code in Visual Studio 2019.
Visual Studio 2019 opens a network connection to a Mac build host anduses the build tools on that machine to compile and sign the iOS app.
There is no need to run a separate application on the Mac – VisualStudio 2019 invokes Mac builds securely over SSH.
Visual Studio 2019 is notified of changes as soon as they happen. Forexample, when an iOS device is plugged in to the Mac or becomes availableon the network, the iOS Toolbar updates instantly.
Multiple instances of Visual Studio 2019 can connect to the Macsimultaneously.
It's possible to use the Windows command-line to build iOS applications.
Note
Before following the instructions in this guide, complete the following steps:
- On a Windows machine, install Visual Studio 2019
- On a Mac, install Xcode and Visual Studio for Mac
- You must manually open Xcode after installing so that it can add any additional components.
If you would prefer not to install Visual Studio for Mac, Visual Studio 2019can automatically configure the Mac build host with Xamarin.iOS and Mono.You must still install and run Xcode.For more information, see Automatic Mac provisioning.
Enable remote login on the Mac
To set up the Mac build host, first enable remote login:
On the Mac, open System Preferences and go to the Sharing pane.
Check Remote Login in the Service list.
Make sure that it is configured to allow access for All users, orthat your Mac username or group is included in the list of allowedusers.
If prompted, configure the macOS firewall.
If you have set the macOS firewall to block incoming connections, youmay need to allow mono-sgen
to receive incoming connections. An alertappears to prompt you if this is the case.
If it is on the same network as the Windows machine, the Mac shouldnow be discoverable by Visual Studio 2019. If the Mac is still notdiscoverable, try manually adding a Mac or takea look at the troubleshooting guide.
Connect to the Mac from Visual Studio 2019
Now that remote login is enabled, connect Visual Studio 2019 to the Mac.
In Visual Studio 2019, open an existing iOS project or create a new oneby choosing File > New > Project and then selecting an iOS projecttemplate.
Open the Pair to Mac dialog.
Use the Pair to Mac button iOS toolbar:
Or, select Tools > iOS > Pair to Mac.
The Pair to Mac dialog displays a list of all previously-connectedand currently-available Mac build hosts:
Select a Mac in the list. Click Connect.
Enter your username and password.
The first time you connect to any particular Mac, you areprompted to enter your username and password for that machine:
Tip
When logging in, use your system username rather than full name.
Pair to Mac uses these credentials to create a new SSH connectionto the Mac. If it succeeds, a key is added to the authorized_keysfile on the Mac. Subsequent connections to the same Mac will loginautomatically.
Pair to Mac automatically configures the Mac.
Starting with Visual Studio 2019 version15.6,Visual Studio 2019 installs or updates Mono and Xamarin.iOS on aconnected Mac build host as needed (note that Xcode must still beinstalled manually). See Automatic Macprovisioning for more details.
Look for the connection status icon.
When Visual Studio 2019 is connected to a Mac, that Mac's itemin the Pair to Mac dialog displays an icon indicating thatit is currently connected:
There can be only one connected Mac at a time.
Tip
Right-clicking any Mac in the Pair to Mac list brings up a contextmenu that allows you to Connect..., Forget this Mac, orDisconnect:
If you choose Forget this Mac, your credentials for the selectedMac will be forgotten. To reconnect to that Mac, you will need to re-enteryour username and password.
If you have successfully paired to a Mac build host, you are ready to buildXamarin.iOS apps in Visual Studio 2019. Take a look at theIntroduction to Xamarin.iOS for Visual Studioguide.
If you have not been able to pair a Mac, try manually adding aMac or take a look at the troubleshootingguide.
Manually add a Mac
If you do not see a particular Mac listed in the Pair to Mac dialog,add it manually:
Locate your Mac’s IP address.
Open System Preferences > Sharing > Remote Login on your Mac:
Alternatively, use the command line. In Terminal, issue this command:
Depending on your network configuration, you may need to use aninterface name other than en0
. For example: en1
, en2
, etc.
In Visual Studio 2019's Pair to Mac dialog, select Add Mac...:
Enter the Mac's IP address and click Add:
Enter your username and password for the Mac:
Tip
When logging in, use your system username rather than full name.
Click Login to connect Visual Studio 2019 to the Mac over SSH and addit to the list of known machines.
Automatic Mac provisioning
Starting with Visual Studio 2019 version 15.6,Pair to Mac automatically provisions a Mac with software necessary forbuilding Xamarin.iOS applications: Mono, Xamarin.iOS (the softwareframework, not the Visual Studio for Mac IDE), and various Xcode-relatedtools (but not Xcode itself).
Important
- Pair to Mac cannot install Xcode; you must manually install it on theMac build host. It is required for Xamarin.iOS development.
- Automatic Mac provisioning requires that remote login isenabled on the Mac, and the Mac must be network-accessible to the Windowsmachine. See Enabling remote login on the Macfor more details.
- Automatic Mac provisioning requires 3GB of free space on the Mac to install Xamarin.iOS.
Pair to Mac performs necessary software installations/updates when VisualStudio 2019 is connecting to theMac.
Mono
Pair to Mac will check to make sure that Mono is installed. If it is notinstalled, Pair to Mac will download and install the latest stable versionof Mono on the Mac.
Progress is indicated by various prompts, as shown by the followingscreenshots (click to zoom):
Mono | Install Check | Downloading | Installing |
---|
Xamarin.iOS
Pair to Mac upgrades Xamarin.iOS on the Mac to match the versioninstalled on the Windows machine.
Important
Pair to Mac will not downgrade Xamarin.iOS on the Mac from alpha/betato stable. If you have Visual Studio for Mac installed, set yourrelease channel asfollows:
- If you use Visual Studio 2019, select the Stable updates channel inVisual Studio for Mac.
- If you use Visual Studio 2019 Preview, select the Alpha updateschannel in Visual Studio for Mac.
Progress is indicated by various prompts, as shown by the followingscreenshots (click to zoom):
Xamarin.iOS | Install Check | Downloading | Installing |
---|
Xcode tools and license
Pair to Mac will also check to determine whether Xcode has been installedand its license accepted. While Pair to Mac does not install Xcode, itdoes prompt for license acceptance, as shown in the following screenshots(click to zoom):
Xcode | Install Check | License Acceptance |
---|
Additionally, Pair to Mac will install or update various packagesdistributed with Xcode. For example:
- MobileDeviceDevelopment.pkg
- XcodeExtensionSupport.pkg
- MobileDevice.pkg
- XcodeSystemResources.pkg
The installation of these packages happens quickly and without a prompt.
Note
These tools are distinct from the Xcode Command Line Tools, whichas of macOS 10.9 areinstalled with Xcode.
Troubleshooting automatic Mac provisioning
If you encounter any trouble using automatic Mac provisioning, take a lookat the Visual Studio 2019 IDE logs, stored in%LOCALAPPDATA%XamarinLogs16.0. These logs may contain error messagesto help you better diagnose the failure or get support.
Build iOS apps from the Windows command-line
Pair to Mac supports building Xamarin.iOS applications from the commandline. For example:
The parameters passed to msbuild
in the above example are:
ServerAddress
– The IP address of the Mac build host.ServerUser
– The username to use when logging in to the Mac build host.Use your system username rather than your full name.ServerPassword
– The password to use when logging in to the Mac build host.
Note
Visual Studio 2019 stores msbuild
in the following directory:C:Program Files (x86)Microsoft Visual Studio2019<Version>MSBuildCurrentBin
The first time Pair to Mac logs in to a particular Mac build host fromeither Visual Studio 2019 or the command-line, it sets up SSH keys. With thesekeys, future logins will not require a username or password. Newlycreated keys are stored in %LOCALAPPDATA%XamarinMonoTouch.
If the ServerPassword
parameter is omitted from a command-line buildinvocation, Pair to Mac attempts to log in to the Mac build hostusing the saved SSH keys.
Summary
This article described how to use Pair to Mac to connect Visual Studio 2019 to aMac build host, enabling Visual Studio 2019 developers to build native iOSapplications with Xamarin.iOS.
Next steps