-->

1. Mac Windows Download
2. Download Microsoft Visual Studio Community

• Difference between Visual Studio Code and Community. Visual Studio Code FAQ. What are the differences between Visual Studio Code and Visual Studio? Disclaimer: Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from the third-party linked sites or any support related.
• Click the Download button on this page to start the download, or select a different language from the Change language drop-down list and click Change. Do one of the following: To start the installation immediately, click Run. To save the download to your computer for installation at a later time, click Save. To cancel the installation, click.
• I am using visual studio C since some days. While programming a C project, I have included the header for example winnt.h. But the compiler says that there are a lot of syntax errors in winnt.h.

Stuck in Applying Microsoft VisualStudio Debugger JustInTime 3 Solution 在线安装VA2017出现问题-Problems with online VA2017 1 Solution Workload selection/deselection works in nonsensical way 1 Solution I can't install my Visual Studio Community 2017 (Ver.15.0.26228.12).

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.

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

• November 24, 2020 - Visual Studio 2019 for Mac version 8.8.2
• November 19, 2020 - Visual Studio 2019 for Mac version 8.8.1
• November 10, 2020 - Visual Studio 2019 for Mac version 8.8

Mac Windows Download

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

• Visual Studio for Mac 8.8 adds preview support for Custom .NET Core templates added with dotnet new (Preview features can be enabled in Preferences > Other > Preview Features).
• Visual Studio for Mac 8.8 adds support for debugging Blazor WebAssembly projects.
• Visual Studio for Mac 8.8 adds support for accessing Azure DevOps NuGet package sources using the signed in account without the need to use a personal access token (PAT).
• Visual Studio for Mac 8.8 now supports running on the macOS Big Sur developer preview. See Known Issues for additional information.
• We added functionality to Visual Studio for Mac to warn users when low disk space will degrade the experience.

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.8.2 (8.8.2.41)

released November 24, 2020

General

• We updated .NET Core to 3.1.404.
• We updated the F# compiler to 5.0.

Debugger

• We fixed an issue blocking operations when multiple watches are selected in the watch tool window.
• We fixed several issues causing the wrong value to be copied or pasted within the watch tool window.
• We fixed an issue where it was not possible to rename a watch while debugging.

Installer

• We fixed an issue where the Installer was not able to download .NET Core and the installation failed.

Shell and Tools

• We fixed an issue where the Errors tool window didn't remember toolbar button settings.

Source Code Editing

• We fixed an issue where F# 4.6 language features don't work on VS for Mac (Stable or Preview).
• We fixed an issue where member _.method in F # was not recognized correctly.
• We fixed build issues causing FS0010 errors with new F# Web projects.
• We fixed an issue where Find References is not working.
• We fixed an issue with the Rename functionality not working correctly.
• We fixed an issue with missing support for FSharp.Core 4.7.
• We fixed various issues with GB18030 encoding support.

Visual Studio 2019 for Mac version 8.8.1 (8.8.1.37)

released November 19, 2020

General

• We fixed several issues with reliability and performance.

Debugger

• We fixed an issue where the Exception window appears outside of the desktop.
• We fixed an issue where the Set Next Statement command failed with an error depending on where the editor caret was placed.

Shell and Tools

• We fixed an issue where loading a solution failed after closing VS for Mac in full screen mode on Big Sur.
• We fixed the code search in the assembly viewer.

Web and Azure

• We fixed an issue where loading Blazor Web Assembly projects failed if the project path contained spaces.

Xamarin

• We fixed an accessibility issue in the XAML Previewer where a decorative image was erroneously being anounced as 'image' by Voice Over.
• We fixed an accessibility issue in the XAML Previewer where unnecessary content was being announced by Voice Over when navigating to the 'Get started with XAML hot reload' link.
• We added support for Xcode 12.2.

Visual Studio 2019 for Mac version 8.8 (8.8.0.2913)

released November 10, 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

Debug Blazor WebAssembly projects

Visual Studio for Mac now includes full support for debugging Blazor WebAssembly projects, giving you the option to set breakpoints, watches, navigate your code using step and skip commands, and more.

For more information on debugging in Visual Studio for Mac, see Debugging with Visual Studio for Mac.

Web and Azure

• We added support for .NET 5 preview 8.
• We added integrated support for accessing NuGet Azure DevOps package sources using the signed in account without requiring a personal access token (PAT).

Bug Fixes

Debugger

• We fixed an issue where the debugger would prefer an imported class over a local variable with the same name.
• We fixed a potential crash/hang after terminating the debugger.
• We fixed an issue where local variables were not evaluated when debugging a Blazor application with .NET 5.

Project System

• We fixed an issue that resulted in an empty properties pad for files when loading AddIn projects.
• We fixed an issue that prevented users from canceling a solution load operation.
• We fixed an issue where the Android build process never stops.
• We fixed an issue where renaming a file with 'Show All Files' enabled in the Solution window added the file twice and might have caused a hang.
• We fixed an issue with VS for Mac setting a different FrameworkSDKRoot.
• We fixed an issue where creating a new project folder with a single character failed with an error.
• We updated MSBuild to 16.8 RTM.

Download Microsoft Visual Studio Community

Shell and Tools

• We increased the speed of the find in files functionality.
• We fixed an issue causing erroneous exceptions to be logged when deleting unsaved files from a project.
• We fixed an issue resulting in multiple searches and unresponsiveness in the search experience.
• We fixed an issue where Visual Studio is unable to find files/classes included into a multi-target SDK style project.
• We fixed an issue where the directory path for find in files was not set correctly.
• We fixed an issue that prevented users drom opening assemblies in the Assembly Browser.
• We fixed an issue that caused files to open in Visual Studio Code instead of in the hex editor when choosing to open in the hex editor.
• We improved the performance of the Assembly Viewer.
• We have ported the Assembly Browser to the new Editor.
• We have reimplemented the Errors pad and moved the build output to a separate pad.
• We have improved overall performance and reliability.
• We replaced the 'Pad' terminology with 'Tool Window' throughout the IDE and updated the top-level View menu.
• We fixed an issue where the content of the 'Reference' dialog was not announced in proper sequence with VoiceOver.
• We fixed a potential hang in the Assembly Browser.
• We fixed an issue with encoding inside the integrated Terminal.
• We fixed an issue where 'Find' in the 'Replace in Files' dialog replaced the found text.
• We fixed an issue where Searching in a Directory failed after the second use.
• We updated NuGet to 5.8 RC.
• We fixed an issue where it was not possible to type (special) characters in the VS console while pressing the option-key.
• We fixed an issue where alerts were not clickable with the mouse on macOS Big Sur.

Source Code Editing

• The F# editor and language service have been updated to use the same backend as Visual Studio (Windows). This fixes a number of issues previously reported on Developer Community including:
  • F# multiply operator as a function wrongly affects color of code after.
  • F# 4.7 language features don't work.
  • Undo doesn't work.
  • Three double quotation marks are placed instead of two.
  • F# 4.7 isn't supported.
  • Editor fails on matching quote insertion.
• We fixed an issue causing the default key binding for 'Navigate To..' to no longer work with the French keyboard.
• We fixed a problem where new F# projects would not restore and build due to the FSharp.Core NuGet package being unavailable.
• We have fixed an issue where an Enum could not be used as a nullable type in generic interfaces.
• We fixed an issue where Design-time error highlighting and Quick Fix suggestions stopped working.
• We fixed an issue with Red underlines not being shown on syntax errors.
• We fixed an issue where inserting code snippets into a C# file failed.
• We fixed an issue where EventHandler completion didn't work.
• We fixed an issue with YAML support.

Test Tools

• We fixed an issue where Running unit tests from the context menu was way slower than from the Unit Tests pad.

Version Control

• We fixed an issue where there was odd behavior when copying files under source control.
• We fixed an issue that could cause hangs when using Git version control.
• We fixed an issue causing version control commits to fail if Git reported fatal: LF would be replaced by CRLF.
• We fixed an issue that disabled view history when a file that's not tracked or a project is selected in the solution pad.
• We fixed an issue where Git integration on Visual Studio for Mac is not working.
• We fixed an issue where deleting a file from project rolls back messing up the Source control.
• We fixed an issue where openinig a project or switching branches on console does not always update the current branch in the project browser.
• 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.
• We fixed an issue where stashing errors were not handeled properly.
• we fixed an issue with broken selection buttons in the 'Review and Commit' view.
• We fixed an issue where the Git configuration dialog blocked use of the IDE and could not be closed.
• We fixed an issue where the status of a copied then pasted file was not updated properly.
• We fixed an issue where an error was shown after copying a file if Git was not installed.
• We fixed an issue where deleting a new file under a newly added folder deleted the empty folder as well.

Web and Azure

• We fixed an issue where a new F# test project will display errors and warnings.
• We fixed an issue with solution file generation that caused a compatibility problem with Visual Studio on Windows.
• We fixed an issue where .razor files would incorrectly show a “Using directive is unnecessary' error.
• We fixed an issue where IntelliSense for classes from a new Razor class library project were not available in .razor files.
• We fixed an issue preventing Azure subscriptions being found when publishing to Azure Publish to Azure.
• We fixed an issue where Azure subscriptions were not found.
• We fixed a crash in the Razor editor.
• We fixed an issue with breakpoints not hitting when debugging a Blazor WebAssembly Application.
• We have added a preview support for Custom .NET Core templates added with dotnet new.
• We fixed an issue where a Blazor WebAssembly project was not recognized as such with .NET 5 and the Browser selection was missing.
• We fixed an issue where an invalid development certificate caused an unrecoverable hang.
• We fixed an issue where IntelliSense shows the OpenAPI client after the OpenAPI service was removed.
• We updated .NET Core to 5.0.100 and 3.1.403.

Xamarin

• We fixed an issue that erroneously changed the simulator to iPad Pro for the designer if Xcode was used to open and add layouts to the Storyboard file.
• We fixed an issue where users were unable to load Storyboards in Visual Studio for Mac.
• We fixed an issue that resulted in Storyboard errors.
• We fixed an issue where adding an Apple account for Xamarin.iOS is broken.
• We fixed an issue resulting in failure to add an Apple developer account with two step authentication.
• We fixed an issue preventing pairing with Visual Studio.
• We fixed an issue where the Storyboard editor would not start.
• We updated the Android SDK Tools path to support the new 'cmdline-tools' path.
• Hot reload updated the minimum required Xamarin.Forms version to 4.6.0.923 when using incremental.
• We fixed an issue where Xamarin Forms Hot Reload caused the iOS Simulator to come to foreground.
• We fixed an issue with the iOS Simulator Window stealing focus multiple times.
• We fixed an issue with Vector Images not appearing in Assets.xcassets.
• We fixed an issue where the target framework of a Xamarin.Mac full framework project kept switching back to Xamarin.Mac Modern.
• We fixed an issue where VS for Mac was removing some default properties from Xamarin.Android projects.
• The Android SDK manager will now prompt to install Android API 28 if it is not already installed to ensure compatibility with the Xamarin.Forms templates.
• We added support for Xcode 12.1.

Other

• We improved startup performance of the IDE.
• We improved the performance of closing a solution.
• We fixed an issue where vstool would not return the exact id of an extension which can then be used for disabling/enabling the extension.

Known Issues

The following is a list of all existing known issues in Visual Studio 2019 for Mac version 8.8:

• After installing the latest .NET 5 SDK, developers of .NET Core 3.1 apps might see an error indicating 'The ASP.NET Core developer certificate is in an invalid state.'. Running dotnet dev-certs https --clean then dotnet dev-certs https --trust from the Terminal will fix the issue.
• Loading Blazor WebAssembly projects with .NET 5.0 RC1 is not yet supported.
• 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.

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.

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:

1. On the Mac, open System Preferences and go to the Sharing pane.

2. 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.

3. 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.

4. 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.

1. In Visual Studio 2019, open an existing iOS project or create a new oneby choosing File > New > Project and then selecting an iOS projecttemplate.

2. 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:

3. Select a Mac in the list. Click Connect.

4. 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.

5. 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.

6. 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:

1. 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.

2. In Visual Studio 2019's Pair to Mac dialog, select Add Mac..:

3. Enter the Mac's IP address and click Add:

4. Enter your username and password for the Mac:

   Tip

   When logging in, use your system username rather than full name.

5. 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.

Our website provides a free download of Facebook Desktop 1.9 for Mac. The application relates to Communication Tools. Our built-in antivirus scanned this Mac download and rated it as 100% safe. This Mac application was originally developed by Charles Bihis. Download facebook on mac. A free program for mac FreeChat for Facebook Messenger is a free program only available for Mac, being part of the category Internet software with subcategory Chat & Communication. MAC Free Download. Download apps for Mac computer and laptops. Facebook video download free download - Adobe Presenter Video Express, YTD Video Downloader, Facebook Exporter for iPhoto, and many more programs.

Progress is indicated by various prompts, as shown by the followingscreenshots (click to zoom):

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):

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):

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