Visual Studio for Mac 8.9 introduces support for Solution Filter (.slnf) files. Visual Studio for Mac 8.9 introduces a new Git Blame view using the native editor. Visual Studio for Mac 8.9 adds a new Quick Actions and Refactoring experience as a preview feature (Preview features can be enabled in Preferences Other Preview Features). The Visual Studio for Mac editor supports powerful built-in refactoring options such as Extract Method and Rename, accessible via the Quick Actions menu. Download Visual Studio Community, Professional, and Enterprise. Try Visual Studio IDE, Code or Mac for free today. Download Visual Studio Community, Professional, and Enterprise. Try Visual Studio IDE, Code or Mac for free today. Download Visual Studio Code for macOS. After clicking on the Mac option on the download site, it will download a zip file, as shown below: Double-click on the downloaded zip to expand the contents. It will give a file, as shown below: Drag “Visual Studio Code.app” to the “Applications” folder, so as it available in the “Launchpad.
-->![Mac Mac](/uploads/1/1/8/8/118803573/115384474.jpg)
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
- April 21, 2021 - Visual Studio 2019 for Mac version 8.9.7
- April 13, 2021 - Visual Studio 2019 for Mac version 8.9.6
- April 6, 2021 - Visual Studio 2019 for Mac version 8.9.5
- March 30, 2021 - Visual Studio 2019 for Mac version 8.9.4
- March 23, 2021 - Visual Studio 2019 for Mac version 8.9.3
- March 16, 2021 - Visual Studio 2019 for Mac version 8.9.2
- March 9, 2021 - Visual Studio 2019 for Mac version 8.9.1
- March 2, 2021 - Visual Studio 2019 for Mac version 8.9
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.9 introduces a new native XML editor.
- Visual Studio for Mac 8.9 uses the native editor inside the Immediate window.
- Visual Studio for Mac 8.9 introduces support for Solution Filter (*.slnf) files.
- Visual Studio for Mac 8.9 introduces a new Git Blame view using the native editor.
- Visual Studio for Mac 8.9 adds a new Quick Actions and Refactoring experience as a preview feature (Preview features can be enabled in Preferences > Other > Preview Features).
- Visual Studio for Mac 8.9 adds support for filtering first chance exceptions by type, module, and function location as a preview feature (Preview features can be enabled in Preferences > Other > Preview Features).
- Visual Studio for Mac 8.9 has full accessibility support enabled by default.
- Visual Studio for Mac 8.9 no longer includes the iOS designer.
- Visual Studio for Mac 8.9 no longer includes the Xamarin.Forms previewer in favor of XAML Hot Reload. For more info see https://aka.ms/xamlhotreload.
- Visual Studio for Mac 8.9 introduces support for version 30 of the Android SDK API.
- Visual Studio for Mac 8.9 adds support for running and debugging unit tests for Unity projects.
- Visual Studio for Mac 8.9 improves the Locals tool window for Unity projects.
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.9.7 (8.9.7.8)
released April 21, 2021
General
- We fixed a couple reliability issues in the Xamarin and Unity experiences.
Debugger
- We fixed an issue where the 'Enable subprocess debugging' option wasn't working correctly.
Version Control
Microsoft Visual Studio For Mac
- We fixed an issue where the scroll position was not in sync between the editor and the blame view.
Visual Studio 2019 for Mac version 8.9.6 (8.9.6.6)
released April 13, 2021
General
- We fixed several reliability issues.
Web and Azure
- We updated .NET Core SDKs to 5.0.202 and 3.1.408.
Tools for Unity
- We fixed a possible crash when retrieving unit tests from the Unity Editor.
Visual Studio 2019 for Mac version 8.9.5 (8.9.5.4)
released April 6, 2021
General
- We fixed several reliability issues.
Visual Studio 2019 for Mac version 8.9.4 (8.9.4.25)
released March 30, 2021
General
- We fixed several reliability and performance issues.
Source Code Editing
- We fixed an issue where Cmd+Click was hard to use / flickering.
Version Control
- We fixed an issue where the editor was read only after using the Git Blame.
Visual Studio 2019 for Mac version 8.9.3 (8.9.3.13)
released March 23, 2021
General
- We fixed several reliability and performance issues.
Web and Azure
- We fixed an issue where preprocessed Razor pages were missing or not precompiled.
Visual Studio 2019 for Mac version 8.9.2 (8.9.2.0)
released March 16, 2021
General
- We fixed several reliability and performance issues.
Version Control
- We fixed an issue where the commit dialog was showing duplicated tooltips
Xamarin
- We fixed an issue where VS for Mac couldn't find Xcode.
- We fixed an issue where [building Android projects failed if the Android SDK was missing].
Visual Studio 2019 for Mac version 8.9.1 (8.9.1.34)
released March 9, 2021
General
- We fixed several reliability and performance issues.
Source Code Editing
- We fixed an issue where it was not possible to go to definition using CMD+Click.
Web and Azure
- We updated the roslyn compiler to address several issues with Blazor and .NET 6.
- We updated .NET Core SDKs to 5.0.201 and 3.1.407 addressing CVE-2021-26701
Tools for Unity
- We fixed an issue where canceling a running test was not working correctly.
Visual Studio 2019 for Mac version 8.9 (8.9.0.1651)
released March 2, 2021
New Features
Project System
- We added support for Solution Filter (*.slnf) files.
Web and Azure
- We added support for .NET 6 workloads and projects.
Tools for Unity
- Added support for running and debugging Unity tests in VS for Mac
- Added
Active Scene
to locals, showing root game objects. - Added
this.gameObject
to locals, given it's widely used in Unity projects. - Added
Children
andComponents
groups to allGameObject
instances, so that you can easily display all the object hierarchy. - Added
Scene Path
to allGameObject
instances, to show the location in the scene. - Added support for
JobEntityBatch
/Lambdas when using Entities with source generators. - Improved support for displaying large arrays (using index bucketing).
- Added support for
raytrace shaders
,UXML
andUSS
files. - Updated Unity messages API (for all methods used as coroutines).
- Updated Android SDK detection.
Bug Fixes
General
- We fixed a critical crash reporting issue.
- We fixed several issues with reliability and performance.
- We updated Mono to 6.12.0.122 addressing CVE-2021-24112
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.
- We fixed an issue where it was not possible to debug 32 bit assemblies using Run > Debug Application.
- 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.
- We fixed an issue where catchpoints didn't work with .NET Core.
- We fixed an issue where Debugging was not working with XCode 12.
Project System
- We fixed an issue where a new project configuration added on VS 2017 on Windows does not load properly on VS for Mac.
- We fixed an issue that could cause the solution tree to be blank under certain conditions.
- We fixed an issue where a changed Xamarin.Forms project was not rebuilt upon deployment.
- We fixed an issue where the evaluation of complex ProjectReference conditions failed.
- We fixed an issue where moving or renaming nested files didn't work.
Installer
- We updated the Android SDK API version to 30.
- We fixed an issue where downloading the .NET Core package failed.
Shell and Tools
- We increased the speed of the find in files functionality.
- We fixed an issue where saving failed after excluding resources from a project.
- We fixed a potential accessibility issue where the color contrast of the integrated terminal's selection color in dark mode is too low.
- We fixed an issue where loading a solution failed after closing VS for Mac in full screen mode on Big Sur.
- We fixed an issue where the Welcome screen close button was invisible on macOS Big Sur.
- We fixed an issue where it was not possible to type special characters in the terminal tool window while pressing the option key.
- We fixed an issue where the build output was shown instead of the error window when clicking on an error inside the status bar.
- We fixed an issue where alerts were not clickable with the mouse on macOS Big Sur.
- We fixed an issue where the Errors tool window didn't remember toolbar button settings.
- We fixed an issue where searching for 'Problems and Solutions' failed sometimes.
- We fixed an issue where the 'Show Start Window' menu item was missing.
- We fixed an issue where it was not possible to restart a project without debugging.
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 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 where Extension Methods navigation search operation was running indefinitely.
- We fixed an issue with missing support for FSharp.Core 4.7.
- We fixed various issues with GB18030 encoding support.
- We fixed an issue where a custom key binding for the Find Caret command was not working in the new editor.
- 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 YAML support.
- We fixed an issue with orphaned Quick Action popups.
- We fixed an issue where IntelliSense stopped functioning in a C# project referencing another F# project.
- We fixed an issue with a low text contrast in lines with a breakpoint.
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 improved the Blame view and made it more accessible.
- We fixed an issue where switching branches got stuck at 'Updating version control repository'.
- We fixed an issue where Visual Studio Mac won't recognize the latest updates to the code.
- 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.
- We fixed an issue where 'Publishing Project' never completed.
- We fixed an issue with where the alert about missing Xcode command line tools was too intrusive.
- We fixed an issue where stashing failed with an error.
Web and Azure
- We updated .NET Core SDKs to 5.0.103 and 3.1.406.
- We fixed an issue where IntelliSense shows the OpenAPI client after the OpenAPI service was removed.
- We fixed an issue where incorrect ASPNETCORE_URLS environment variable was generated when debugging apps.
- We fixed several issues where dynamic parameters were not loaded correctly from some custom templates.
- We fixed an issue where loading Blazor Web Assembly projects failed if the project path contained spaces.
- We fixed an issue where publishing ASP.NET Core 5.0 projects to Azure failed with an 'HTTP Error 500.31 - ANCM Failed to Find Native Dependencies' error.
- We fixed an issue with debugging Azure Functions locally.
Tools for Unity
- Fixed search highlighting in Unity message dialog.
- Fixed stability issues with Unity project treeview.
- Fixed handling of conditional breakpoints.
- Fixed stability issues with Unity message dialog
- Fixed various UI issues for non ENU languages.
- Fixed stability issues with
UNT0018
diagnostic. - Fixed VM disconnection issues when using
Trace
methods. - Fixed filtering of obsolete properties throwing exceptions.
- Fixed
UNT0006
diagnostic, giving wrong warnings for Coroutines andAssetPostprocessor.OnAssignMaterialModel
. - Added missing Unity messages for 2019.4 API.
Xamarin
- We added support for Xcode 12.4.
- The iOS designer is no longer part of Visual Studio for Mac. We have made improvements to our Xcode sync process to help you adapt to using Xcode to design your Xamarin.iOS storyboards. See Designing user interfaces with Xcode - Xamarin | Microsoft Docs to learn more.
- The Xamarin.Forms previewer is being removed in favor of XAML Hot Reload. For more info see https://aka.ms/xamlhotreload.
- We fixed an issue where Xamarin project files were always shown as edited in git.
Known Issues
The following is a list of all existing known issues in Visual Studio 2019 for Mac version 8.9:
- 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
thendotnet dev-certs https --trust
from the Terminal will fix the issue. - 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.
- If you're already on Big Sur and can't use the updater, visit the Visual Studio for Mac website and download the installer.
- On Big Sur gRPC projects may fail to build with an error
protoc' exited with code 255
. This is a problem with macOS platform detection in the gRPC.Tools NuGet package that is used by default in the project templates. A workaround is to update the gRPC.Tools NuGet package to version 2.34.0 or later.
In Visual Studio for Mac, you can add an EditorConfig file to your project or solution to enforce consistent coding styles for everyone that works in the codebase. The settings declared in the EditorConfig file take precedence over global Visual Studio for Mac text editor settings. Using an EditorConfig file within your project or codebase allows you to set your coding style, preferences, and warnings for your project. Because the file is part of your codebase, it makes it easier for all users to adhere to the coding practices of a project, regardless of the IDE or code editor that they use.
EditorConfig files are supported on many IDEs and code editors, including Visual Studio.
Supported settings
The editor in Visual Studio for Mac supports the core set of EditorConfig properties:
indent_style
indent_size
tab_width
end_of_line
charset
trim_trailing_whitespace
insert_final_newline
root
EditorConfig also supports Coding conventions in C#.
Add an EditorConfig file to a project
Adding a new EditorConfig file
- Open your project in Visual Studio for Mac. Select either the solution or project node that you wish to add the EditorConfig file to. Adding the file to the solution directory applies the .editorconfig settings to all projects in the solution.
- Right-click on the node and select Add > New File to open the New File dialog:
- Choose Misc > Empty Text File and give it the Name
.editorconfig
. Press New to create the file and open it in the editor:Adding the item at the solution level automatically creates and nests it in a Solution Items folder: - Edit the file. For example:
- Read kindle books on mac. The settings from the
.editorconfig
file will apply to any new code that you write, but existing code may need to be reformatted to be consistent with the new settings. To apply the settings from the.editorconfig
file to an existing source file, open the file and choose Edit > Format > Format Document from the menu bar::
Adding an existing EditorConfig file
If you're working with a project or solution that already contains an
.editorconfig
file, there is nothing that you need to do to apply the settings. Any new lines of code are formatted according to the EditorConfig settings.You may want to reuse an existing
.editorconfig
file in your project. To add an existing file, do the following:- Right-click on the folder you wish to add it to and select Add > Add Files.
- Browse to the directory of the required file.
- Files beginning with
.
(such as.editorconfig
) are hidden files in macOS, so press Command + Shift + . to make the.editorconfig
file visible. - Select the
.editorconfig
file and click Open: - When you're presented with the following dialog, select the Copy the file to the directory option and select OK:
Reflecting .editorconfig settings
Once you add an EditorConfig file to your codebase, any new code added is automatically formatted according to the specified settings. Existing code doesn't automatically reflect the settings unless you format the codebase.
Visual Studio Editor Download
To reflect the settings from the
.editorconfig
file, select the solution node and choose Edit > Format > Format Document from the menu bar:Editing an EditorConfig file
EditorConfig files use a straightforward file layout to specify settings, which is explained below using a previous example: Susanna moore memoir books.
Setting
root
to true
flags this file as the top-most file of the codebase and any higher .editorconfig
files in the project are ignored, as explained in the Override EditorConfig Settings section.Each section is denoted by square ([ ]) braces and specifies information on the types of files the following properties should pertain to.
Visual Studio Editor For Mac
In the example above, some settings are applied to all files in the project and others are added only to C# files. The screenshots below show before and after the
.editorconfig
settings have been applied:Before:
After:
For more information on available EditorConfig settings, see the .NET coding convention settings for EditorConfig article and the Supported Properties section on the official documentation.
Override EditorConfig Settings
Visual Studio For Mac Tutorial
It's possible to have more than one
.editorconfig
file in each solution. Visual Studio for Mac reads .editorconfig
files from top to bottom in the solution, adding and overriding settings as it goes.This means that the settings in the .editorconfig
closest to the file you're editing will take precedence. Settings are taken from the .editorconfig
file the same folder (if it exists), then the .editorconfig
in parent folder (if that exists), etc. until it finds root=true
.If you want to ensure that no settings from any higher-level
.editorconfig
files are applied to this part of the codebase, add the root=true
property to the top of the lower-level .editorconfig
file: