Visual Studio 2019 for Mac Release Notes
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 Requirements and Mac Platform Targeting and Compatibility guides.
For instructions on installing and updating Visual Studio 2019 for Mac, see the Install Visual Studio for Mac guide.
To learn more about other related downloads, see the Downloads page.
Visual Studio 2019 for Mac (version 8 and higher) is not supported on Mac OS X 10.11 (El Capitan) or lower. If you have Visual Studio 2017 for Mac (version 7), you will not be shown an update to Visual Studio 2019 for Mac. Installation will also be blocked. To resolve this issue, update to macOS 10.12 (Sierra) or higher
What's New in Visual Studio 2019 for Mac
Visual Studio 2019 for Mac version 8.0 Releases
- May 14, 2019 – Visual Studio 2019 for Mac version 8.0.6
- April 29, 2019 – Visual Studio 2019 for Mac version 8.0.5
- April 18, 2019 – Visual Studio 2019 for Mac version 8.0.4
- April 15, 2019 – Visual Studio 2019 for Mac version 8.0.3
- April 9, 2019 – Visual Studio 2019 for Mac version 8.0.2
- April 4, 2019 – Visual Studio 2019 for Mac version 8.0.1
- April 2, 2019 – Visual Studio 2019 for Mac version 8.0
Visual Studio 2019 for Mac Blog
The Visual Studio 2019 for Mac 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:
- This release contains a preview of the next generation text editor for Visual Studio for Mac.
- We've introduced a new getting started experience.
- We've added support for easily running multiple instances of the IDE.
- We've added a new way to set multiple startup projects, making it easier to create a solution Run Configuration that will launch multiple projects when debugging.
- Visual Studio for Mac can now detect that updates to Azure Functions templates are available, and will provide you with a dialog to update them.
- We've improved the debugging experience for Unity projects by sharing the debugger used by Visual Studio Tools for Unity on Windows.
- We have added support for Microsoft Account authentication with Git and Azure DevOps/Team Foundation Server.
- We've moved from having three channels: Alpha, Beta, Stable to just Preview and Stable. You can access updates from the Visual Studio > Check for Updates… menu item.
released May 14, 2019
This release addresses an issue that can lead to a crash when rendering breakpoints in the editor.
released April 29, 2019
We fixed the following issues in this release:
released April 18, 2019
We fixed the following issues in this release:
- Android crashes every time with the VS for Mac 2019
- A corresponding Xamarin.Android SDK is also being released at this time. You can read more information about this issue on GitHub.
- The IDE would crash when quickly undoing changes in the editor after pasting.
released April 15, 2019
We fixed the following issues in this release:
- The IDE would crash when selecting a wrong Azure DevOps account.
- The start window would crash unexpectedly on a Mac with a touchbar.
- The IDE would crash when closing the start window
- Solution Explorer click / selection is not functioning properly
- Visual Studio for Mac does not remember window position
- We didn't show the correct layout for .cs files when opening them.
- You could not stop SmartHotel360 solution build due to too many modules being restored.
- You were unable to create a watchOS solution from the template.
released April 9, 2019
This release adds support for Xcode 10.2.
We fixed the following issues in this release:
- The IDE Shell showed on first launch because of NPS prompt, this meant that you had to quit and restart to use the IDE.
- NullReferenceException is throwing after deleting VSMac preferences, causing issues with the updater.
- Visual Studio freezes when closing and opening a solution from welcome in full screen.
- Templates for .NET Core not found.
- Scrollbar should adhere to macOS preferences in the Start Window.
- Change the project target causes Visual Studio to crash.
- About Visual Studio Modal dialog positioning is off.
- Updater breaks update all the products if there is an exception from any product.
released April 4, 2019
- We fixed an issue where the IDE would crash if the Start Window was closed while a project was being created.
released April 2, 2019
- We've given the Visual Studio for Mac Installer a fresh look with updated icons, splash screens, and carousel screens with useful content for all developers.
- We added support for a minimum version of macOS required for Visual Studio for Mac (10.12). If you're not on macOS 10.12 of newer the installer now prompts you to upgrade your version of macOS.
- We changed our installer defaults to a smaller and smarter install. Instead of selecting everything by default, we select the IDE and .NET Core for all users, and only select iOS or Android if any version of Xcode or Android SDK is detected on your machine.
- If you are developing Xamarin.iOS or Xamarin.Mac apps, we now prompt you to update to the recommended version of Xcode, if you don't already have it installed.
- We removed the NDK from the Android SDK download.
- We made many improvements to the Android permissions dialog, including improving the UI and allowing the user to uncheck Xamarin.Android.
With this release, we've introduced a brand new way of interacting with your projects and getting you to where you need to go in the IDE.
If you're a new Visual Studio for Mac user, you'll be prompted to log in when you first open the IDE. By logging in you can activate your Professional or Enterprise account or connect to Azure. If you're not ready to sign in, you can press the Skip button and sign in through the Visual Studio > Sign In menu item.
You'll then be greeted with the new start window. This window has three main sections, allowing you to create or open new and existing projects:
- Recent Projects: Here you can find a list of your 25 most recent projects. You can optionally "pin" your most frequently used project, if you'd prefer to keep them at the top of the list. The search box can be used to filter through all recent projects in the list.
- Open: You can open any .csproj, .fsproj, .sln or any other supported file from your local directory using this button.
- New: You can select from the many pre-populated templates to help you get started with a new project. The new project dialog will take you through all the necessary configurations to help you get up and running.
New Code Editor
Visual Studio for Mac 2019 contains a preview of the next generation text editor for Visual Studio for Mac! This new text editor shares the same core components with Visual Studio Windows, with an entirely new, native user interface.
At this time, the new editor supports C# files only. Additional language support will be added in future releases.
The new Visual Studio for Mac editor brings the following features:
- Native macOS (Cocoa-based) user interface (tooltips, editor surface, margin adornments, text rendering, IntelliSense)
- Support for native text inputs
- RTL/BiDi language support
- Common Visual Studio Platform core
- Roslyn 3
- Multi-caret support
- Word Wrap
- Update IntelliSense UI
- Improved Find/Replace
Exceptions now use the Cocoa UI to display exception messages, including exception notification and details:
Context Menu Navigation is enabled. You can now use context menu based navigation commands like "Go to Declaration" and "Go To Implementation". We have also enabled "Remove and Sort Usings".
How to enable or disable the editor
As the new editor is a preview feature within Visual Studio for Mac 2019, you have to opt-in to use the feature. Go to the Visual Studio > Preferences… > Text Editor > General section and check the Open C# files in the New Editor checkbox. Once this option is checked, any newly opened C# files will be using the new editor. You will know the new editor is enabled when the "New Editor Preview" button appears in the bottom-right of the editing window.
To disable the new editor, either click the New Editor Preview button in the bottom right of the editor pane and select Disable the New Editor Preview or navigate to the Visual Studio > Preferences… > Text Editor > General section and un-check the Open C# files in the New Editor checkbox.
How to Report a Problem with the editor
To report a problem in the new editor, either click the "New Editor Preview" button in the bottom right of the editor pane and select "Report a Problem". You can also go directly to Developer Community.
Support for multiple instances
Visual Studio for Mac now supports opening multiple instances of the IDE from the dock. Visual Studio for Mac has always had support for opening multiple solutions in one window but we’ve heard a lot of requests to support multiple windows for the IDE. To open a new instance, right-click on the icon in the dock and select New Instance:
Set Startup projects
A new command, Set Startup Projects, is available to make it easier to create a solution Run Configuration that will launch multiple projects when debugging. For information on setting multiple startup projects, see the documentation.
Debugging improvements for Unity
In this release we've replaced the debugger that's used for Unity projects with the debugger from Visual Studio Tools for Unity on Windows. This change has better compatibility with older versions of Unity, improvements for debugging unsafe C# code, and provides better reliability.
Xamarin developers should find a ton of improvements in this release. New highlights include:
We know that developers run through the build-deploy-debug cycle countless times a day, and we're consistently working towards shortening the inner development loop even more. In this release, we've made huge gains by optimizing incremental builds and deployments.
Using the SmartHotel360 app for testing, incremental build times have been trimmed by up to 29%, and deployment times are up to twice as fast. A full report of build performance profiling and methodology is available on the Xamarin.Android wiki, but here’s a quick overview:
|Step||Visual Studio 2017||Visual Studio 2019||Delta|
|Incremental Build (XAML Change)||00:10.62||00:07.47||-29.66%|
|Deploy (XAML Change)||00:09.03||00:04.44||-50.83%|
Our mission to continually increase build reliability continues and one area we've made optimizations to is Android resource updates. By minimizing scenarios where resource updates would occur at build time, there should be a significant reduction of build issues stemming from conflicts in this area.
In a step towards parity with the Android in Visual Studio on Windows experience, the deployment process has been further streamlined and the Android emulator will now launch when starting a build.
The brand-new template for Xamarin Forms Shell projects is now available, and for a more uniform experience across IDEs, this release also includes new file templates previously available only in Visual Studio on Windows. You can use the new XAML files today by navigating to File > New File… > Forms in the Visual Studio 2019 for Mac menu. The new file items are:
- Forms ListViewPage XAML
- Forms MasterDetailPage XAML
- Forms TabbedPage XAML
- Forms ViewCell XAML
And to help make productivity a touch better, Intellisense in Xamarin.Forms XAML files for FontFamily support is now available:
We now have support for Android Pie (9.0)! Additionally, we made enhancements to increase Android Designer start up time and improved scrolling widget support.
This release also ships support for adding “standard” XML namespaces to documents when a corresponding attribute is set, as well as support for escape sequences like '@', '?' and Unicode escape sequences.
We’ve added support for PDF as an image format, and improved support for color spaces and color precision. Additionally, you can now select named colors from asset catalogs as the value for color properties.
We now have support for custom controls that need to load native dynamic libraries or frameworks (note that static libraries are not supported). Additionally, custom properties of type CGSize will now appear in the property panel for custom controls
Azure Functions improvements
We have updated Azure Functions runtime and templates (CLI) in this release. In addition, Visual Studio for Mac will offer you the ability to update your function templates if new templates are available when creating a new Functions project. To update Azure Functions templates, select the update button next to the text "Updated templates are available":
Visual Studio for Mac also supports Azure Functions CLI installed via HomeBrew and will choose the instance with the highest discovered version.
The following issues have also been fixed in this release.
- We fixed an issue where pasting verbatim strings removes double quotes.
- We fixed an issue where the caret location in quick fix margin is incorrect.
- We fixed a performance issue where correcting indentation is taking up too much time on large files.
- We fixed an issue where Intellisense soft-selection is confusing.
- We fixed an issue where Visual Studio for Mac can't open .targets files.
- We fixed an issue where the display updates partially when commenting a collapsed method.
- We fixed an issue where C# syntax highlight doesn't work for some of the keywords.
- We fixed an issue where invoking some snippets from the toolbox in .cs files leads to poorly formatted code.
- We fixed an issue where pressing Down to choose the closing tag completion in XAML IntelliSense closes the completion window.
- We fixed an issue where the file 'redacted' could not be opened.
- We fixed an issue where sometimes pasting fails in XAML files.
- We fixed an issue where, when adding an attribute via Intellisense, it does not trim "Attribute" from the name.
- We fixed an issue where moving a line of source code up or down locks up the editor.
- We fixed an issue where Visual Studio is incredibly CPU-hungry.
- We fixed an issue where tab width is not respected.
- We fixed an issue where you cannot drag forms items from the Toolbox to the XAML editor.
- We fixed an issue where breakpoints do not move as you add lines to text editor.
- We fixed an issue where trying to select collapsed XAML crashes the IDE.
- We fixed an issue where another region opens when entering a directive.
- We fixed an issue where Fold Regions By Default has no effect.
- We fixed an issue where Visual Studio for Mac code snippet for "Exception" inserts incorrect code.
- We fixed an issue where compile errors in non-active tabs can corrupt the active tab.
- We fixed an issue where Visual Studio for Mac becomes unresponsive when selecting two column view.
- We fixed a focus issue where changing tab doesn't allow you to type.
- We fixed an issue where Source Code Analysis is causing typing latency.
- Updated the editor to utilize the vs-platform editor core
- Updated Roslyn to version 3
- We fixed an issue where auto completion chooses the wrong variable name.
- We fixed an issue where Using statement indenting is incorrect.
- We fixed an issue where Smart semicolon placement causes incorrect semicolon placement.
- We fixed an issue where when I move a method parameter to a new line, it no longer aligns the parameter to the previous parameters column.
- We fixed an issue where Visual Studio Community for Mac - crashes when holding down cursor key.
- We fixed an issue where Visual Studio for Mac is inserting matching braces even though the option is disabled..
- We fixed an issue where sometimes updating a package changes its Reference ItemGroup.
- We fixed an issue where updating a package reference adds a relative path to HintPath.
- We fixed an issue where an invalid C# file is created with a new library project.
- We fixed an issue where it is not possible to create a culture specific .resx file through the 'New File ..' menu in the Solutions Explorer context menu.
- Copy/Paste of a XAML file causes a disassociation between the .xaml and .xaml.cs files.
- We fixed an issue where files are being added to ItemGroup.Compile(Remove) and this related issue - Error type of namespace not found.
- We fixed an issue where you are unable to set the Build Action "GoogleServicesJson" when adding a package that references Google Play Services Basement and deploying an application.
- We fixed an issue where reloading a project does not update the project for the Document.
8.0have been removed from the list of C# languages in project options as they do not work with the current Mono.
- Projects with multiple TargetFrameworks now show dependencies for each framework in the Dependencies node in the solution pad.
- We fixed an issue where there were multiple inline type resolution errors for references to signed libraries from non-signed libraries. A similar issue is also present for SDK style projects.
- We fixed an issue where the Type System would not be updated after saving the project file after editing it in the editor.
- We fixed an issue where conditions on PackageReferences were not respected.
- We fixed an issue where Visual Studio Mac does not support item condition.
- We fixed an issue where Visual Studio for Mac cannot build an F# .NET Core solution.
- We fixed an issue where the wrong text color is used in an unfocused but selected row in the structured build output window.
- We fixed an issue where creating a new folder in the Solution Explorer does not let you name the folder at the same time.
- Start Debugging after Start without Debugging results in an exception for ASP.Net projects.
- The Run Item command on the Solution Explorer has been renamed to Run Project.
- Visual Studio for Mac will now use HttpClient and the native Mac networking API when making web requests for nearly all its requests. Some areas have not yet been updated to use HttpClient and the Mac networking API available through Xamarin.Mac's NSUrlSession. The Mac's networking API provides its own built in support for proxies. Visual Studio for Mac can also be configured to use Mono's networking API as an alternative. Some areas are not yet supported such as the sign in dialog, and will continue to use Mono's networking API.
- We fixed an issue where not seeing Code Formatting policies in the UI.
- We fixed an issue where VisualStudio for Mac cannot change projects from C# -> F# or vice versa.
- We fixed an issue where it was not possible to delete entries from Toolbox Clipboard Ring for XAML files.
- We fixed an issue where focusing out/into Visual Studio changes the default focused element on the UI.
- We fixed an issue where navigation history removes files from history.
- We updated items in the help menu.
- We fixed an issue where you cannot set focus in 2 column edit mode with 2 solutions open.
- We updated the "About" dialog window title to be more human readable.
- We fixed an issue where some windows appear positioned incorrectly.
- We fixed an issue where Adding Files modal progress window obscures copy/move modal.
- We fixed an issue where View Archives appears in the context menu of .NET Core projects.
- We fixed an issue where you are unable to create an NUnit Tests project for .NET Core 2.2.
- We fixed an issue where .NET Core console projects use the project directory as the working directory by default instead of the output directory.
- We fixed an issue where .NET Core 3.0 can be selected in New Project dialog when not supported.
- We fixed an issue where the Create button doesn't create a new project for 3.0 preview 2.
- We removed the VB.NET option from .NET Core projects.
- We fixed an issue where templates that come with an API backend did not have a run configuration that launches both projects.
- We fixed an issue where Navigate -> Implementing Members in ASP.NET Core project doesn't work.
- We fixed an issue where Convert Solution Format doesn't do anything for a solution with an ASP.NET Core web app.
- NuGet package diagnostic warnings are now shown in the Solution Explorer. Any diagnostics warnings will be rendered with a warning icon and the full text of the warning available as a tool tip.
- We fixed an issue where NuGet Copyright metadata is not saved.
- We fixed an issue where Visual Studio for Mac crashes after "Could not add packages" error.
- We fixed an issue where NuGet packages are not restored for ASP.NET projects.
- We fixed an issue where conditional NuGet PackageReferences in multi-targeting projects are not supported.
- We fixed an issue where problem while restoring NuGet packages which don't have stable version.
- We fixed an issue where referencing packages conditionally using variables does not work correctly.
- We fixed an issue where Xamarin.Forms app with multi target framework library referenced fail to build.
- We fixed an issue where .ts files are not working in VSMac.
- We fixed an issue where Visual Studio for Mac 2019 cannot open Docker projects.
- We fixed an issue where Visual Studio for Mac crashes on copy & paste in launchSettings.json.
- We have removed the Live Player from Visual Studio for Mac.
- We fixed an issue where the Help -> Release Notes linked to the wrong place.
- We fixed an issue where the toolbox regressed Android designer usage.
- We fixed an issue where a .css file added to .NET Standard Library project is not included in the project despite initial appearance.
- We fixed an issue where XAML Previewer has a problem rendering.
- We fixed an issue where the initial launch of the Xamarin Forms previewer took a long time to render.
- It is now possible to choose .pdf files for image assets that do not support vector images.
- We fixed an issue where it is not possible to choose devices for named colors in the asset catalog.
- We fixed an issue where Native References not working in iOS library projects and appear to be ignored.
- We fixed an issue where deleting a Native Reference does not delete the the file on disk.
- We fixed an issue where the Debugger doesn't connect to a keyboard extension on any device.
- We fixed an issue where signing in with an Apple account fails with "Apple portal sync error: Failure has occurred while loading a type".
- We fixed an issue where Visual Studio for Mac has problems with partial Xcode installs.
- We fixed an issue where the warning when there's no Xcode installed is not very clear.
- We fixed an issue where it is not obvious how to add a new asset item when there is a large number of items.
- We fixed an issue where provisioning profiles for iOS are not sorted correctly.
- We fixed an issue where Visual Studio Mac keeps hanging with iOS projects open.
- We fixed an issue where the incorrect ClassKit entitlement value is included in the archive when archiving for publishing.
- We have removed support for listing and showing Xamarin Android Player emulators.
- We fixed an issue where new Android apps have uppercase letters in the package name.
- We fixed an issue where the casing of
strings.xmlwas inconsistent for new projects.
- We fixed an issue where opening the Report A Problem dialog also displays "Install JDK" dialog.
- We fixed an issue where new projects do not have the min and target API set correctly.
- We fixed an issue where the Android ‘WebView App’ template does not have a ‘Modern Development’ option in project creation dialog.
- We fixed an issue where the Android Emulator Launch in Visual Studio for Mac is extremely slow.
- We fixed an issue where running the Android app does not start with "HAXM" on Visual Studio for Mac 2019.
- We now start the Android emulator when starting to build the project.
- Users can now choose between AAPT and AAPT2 in Xamarin.Android project settings.
- We fixed an issue where deploying to device hangs at 100%.
- We fixed an issue where it was not possible to cancel starting an Android emulator, and having to force quit Visual Studio for Mac if the image was broken.
- We fixed an issue where, if there were multiple Android .csproj files for a project (using different Android Manifests with differing package names), would produce incorrect or invalid archive and would fail to publish.
- We fixed an issue where the JDK notification was shown on the welcome page, even for non-Android projects.
- We fixed an issue where the Android resource update could occur at the same time as a build which could then cause build issues.
- We fixed an issue where it is not possible to change the target framework version for Xamarin.Mac full on re-opening project options.
- We fixed an issue where .xib templates seem to need
- We fixed an issue where macOS 10.13 doesn't show up as a deployment target.
- We fixed an issue where the default platform of macOS projects is x86, but should be AnyCPU.
- We fixed a performance issue where the "Test Results" pane has bad performance when very large amounts of text are shown.
- We fixed an issue where xUnit theories don't execute in Visual Studio for Mac.
- We fixed an issue where Visual Studio for Mac could not load unit tests in an existing solution.
- We fixed an issue where, using NUnit, typing inside Assert.That() pops up a Create method dialog that gets in the way.
- We fixed an issue where Run Test when mapped to a keyboard shortcut doesn't do anything.
- We fixed an issue where 64 bit unit testing is not supported.
- We fixed a number of accessibility issues in this release, including several VoiceOver issues in the Debugger and in creating iOS developer certificates, and Keyboard issues in the Android SDK Manager.
We have added support for Microsoft Account authentication with Git and Azure DevOps/Team Foundation Server, which previously would continually prompt for credentials without successfully connecting.
- We've fixed a set of issues across the product where file edits are some times missing when making Commits/Pushes using Git.
- We fixed an issue where the Merge view was not hidden if there is no merge pending for the current file.
- We fixed an issue with the Blame view where there was no way back in history once you select to show blame before the current commit.
- We fixed an issue where the copy command doesn't respect the focus and always copies the diff of the selected entry.
- We fixed an issue where can't access remote repositories over SSH in Visual Studio for Mac.
- We fixed an issue where switching to Authors tab should jump to the context line, not to the "cached" line state.
- We fixed an issue where The project .sln and .csproj files are deleted when you switch branches using git.
- We fixed an issue where the Version Control -> Update option doesn't prompt before deleting files.
- We fixed an issue where sln and csproj files are not pushed.
- We fixed an issue where git will randomly not add new files as part of the commit operation.
- We fixed numerous usability issues with the Version Control dialog box.
- We fixed an issue where a Null reference is thrown in VersionControl after modifying solution file outside IDE.
- We fixed an issue where manually staged changes disappear from the file status in IDE.
- We fixed an issue where Git log window can beach ball for several seconds when changing selection.
- We fixed an issue where Error "Safe Handle has been closed" appears when changing branch.
- We fixed an issue where .git/index appeared, empty, causing strange issues with staging.
- We fixed an issue where Visual Studio Mac creates a lot of problems when switching branches.
- We fixed an issue where the source control dialogs appear on top of other apps.
- We fixed an issue where users Can't connect to Azure DevOps/git using Visual Studio for Mac and O365 credentials.
- We fixed an issue where Visual Studio for Mac 7.8.1 prompts for git credentials.
- We fixed an issue where Visual Studio for Mac prompts for Git Credentials every time "Update Solution" or "Push Changes" is called.
- We fixed an issue where
git pushprompts for credentials when not needed.
- We fixed an issue that was causing a deadlock when updating the status view.
- We fixed an issue where Git HTTP Auth fails if no username is provided.
- We fixed an issue where using the debugging visualizer for color crashes the IDE.
- We fixed an issue where you can't create breakpoints after using the "Debug an Application" command.
- We fixed an issue where the debugger caused Visual Studio for Mac to crash.
- We fixed an issue where C# debugging operation is silently ignored if you point to non-existent directory to run.
- We fixed an issue where an image from
Xamarin.Forms.UriImageSourceis not displayed in the debugger’s visualiser window when debugging a Xamarin.Forms application.
- We fixed an issue where the debugger would fail when running on an external console on Mojave.
- We fixed an issue where Roslyn fatal exception (System.ArgumentOutOfRangeException).
- Azure functions is now two words in the New Project Dialog.
- We fixed an issue where a NullReferenceException is thrown after deleting VSMac preferences.
- We fixed an issue where the Android Permissions were causing the application to hang.
- We improved the error reporting for individual components and will not show the error page right away.
- We fixed bug where symlinks were breaking when an older Visual Studio for Mac version was copied for backup.
- We fixed a bug where non-retina/low-res icons are being displayed everywhere.
- We fixed an issue where checking for updates can result in multiple prompts to sign in.
- We fixed an issue where updating without restarting can cause strange MSBuild errors.
- We fixed an issue where selecting C# 8 breaks solution preferences dialog in Visual Studio for Mac 2019.
- We fixed an issue where nothing launches when running Help | API Documentation.
- We fixed an issue where there is a possible leak of large data via AsyncOperation.
- We have addressed many accessibility issues as we progress toward making Visual Studio for Mac more accessible.
- We fixed an issue where the updater app is shown in the recent apps in the Dock on macOS Mojave.
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.
The following is a list of all existing known issues in Visual Studio 2019 for Mac version 8.0:
- Visual Studio for Mac prompts for microphone access when starting an Android emulator – Upstream, see https://jira.appcelerator.org/browse/TIMOB-26486?attachmentViewMode=list
- Building a .NET Core or ASP.NET Core 2.2 application inside Visual Studio for Mac will fail if you have the .NET Core 3 Preview 3 or higher SDKs installed on the machine.
- [Workaround] To work around this issue, consider uninstalling the .NET Core Preview SDKs on the machine using this script: https://github.com/dotnet/cli/blob/master/scripts/obtain/uninstall/dotnet-uninstall-pkgs.sh. Then, reinstall the .NET Core 2.2 SDK from https://dotnet.microsoft.com/download
Visual Studio for Mac Release Notes History
You can view prior versions of Visual Studio 2017 for Mac release notes on the Release notes history page.