If you are accessing this page from a non-English language version, and want to see the most up-to-date content, please visit this Release Notes page in English.
You can switch the page language at the bottom of this page. Click the globe icon, search for your language, or select from the list of available languages.
This article contains information about the newest release for Visual Studio 2017 for Mac version 7.1.
Use Visual Studio 2017 for Mac to build apps for mobile, web, and the cloud with Xamarin and .NET Core, as well as games with Unity.
To learn more about other related downloads, see the Downloads page.
How are we doing?
We’d love to hear from you! You can report a problem via the Report a Problem option in the upper right hand corner of the Visual Studio for Mac IDE itself. You can track your feedback in the Developer Community portal.
Release Date: September 19, 2017 - Visual Studio for Mac 184.108.40.206
This release adds support for Apple's Xcode 9 release.
Release Date: September 11, 2017 - Visual Studio for Mac 220.127.116.11
This release fixes the following issue:
- Selecting Apple Developer Account in Preferences crashes Visual Studio for Mac when Xamarin Mac extension is disabled.
Release Date: August 14, 2017 - Visual Studio for Mac 18.104.22.1687
This release focused on bug fixes and introduces the following new features:
- Support for building applications using .NET Core 2.0.
- iOS signing workflow updates.
.NET Core 2 support
Visual Studio for Mac supports building .NET Core 2.0 applications, including libraries, console apps, as well as web applications and services with ASP.NET Core.
Note that the .NET Core 2.0 SDK needs to be installed via a separate download to enable .NET Core 2.0 development in Visual Studio 2017 for Mac Version 7.1. You can get it at www.dot.net/core. Visual Studio enables side-by-side support of multiple .NET Core SDKs. This also means you can experiment with the latest daily build of the .NET Core SDK, while also developing with the latest public releases.
iOS signing workflow updates
This release introduces the ability to create required signing artifacts for iOS and tvOS apps. With Visual Studio for Mac, it's possible to:
- Create new signing identities and install them to the local Keychain.
- Create new Provisioning Profiles.
- Add a new signing identity to an existing profile.
- Provision new devices: register a device in the Apple Developer Portal and add them to a provisioning profile.
To try out these new signing features right-click on your project and browse to Options > iOS Bundle Signing.
Using the Signing Identity section
Before signing, you must satisfy the following criteria:
- A valid certificate (not revoked) is displayed on the Apple Developer Portal in the "Certificates" section.
- The certificate is issued for selected team/developer.
- Both certificate and private key should be installed in your local Keychain.
- Certificate should not be expired.
Use Create signing identity... option of the dropdown if no identities are available on your current machine.
Using the Provisioning Profile section
In order to be shown in the "Provisioning Profile" drop-down profile must satisfy the following criteria:
- Not expired.
- Valid (include registered devices and valid certificates).
- Match current distribution type (Debug or Release based on switches at the top).
- Match bundle identifier. Wild card profiles with a matching pattern will be also displayed in this list.
Use Create provisioning profile... item of the dropdown if no profiles were found.
If you need to switch back to the previous version of signing controls, and set the provisioning profile and signing identity manually, set the team to None. New signing controls will be replaced with old ones. However, we strongly encourage you to try new functionality and provide us with feedback in case of any problems.
- Provisioning profiles created in Visual Studio for Mac will not take into account entitlements selected in your projects (Entitlements.plist). This functionality will be added in future versions of the IDE.
- Distribution provisioning profiles by default will target App Store. In House or Ad Hoc profiles should be created manually.
Fixes in this release
Android SDK Manager
- Android SDK Manager is now integrated within Visual Studio
Preferencesinstead of being an external application.
- Fixed: The Android SDK Manager shows the wrong component status after an aborted installation.
- Fixed: Android SDK Tools installed but not selected if update is available which can result in the component being uninstalled unintentionally.
- Fixed: Default Android SDK location is not saved if no SDK component changes have been made.
- Improved performance for opening, rendering, typing in a document.
- Optimized background work done while typing.
- Improved load time of opening a solution.
- Optimized loading the search bar results.
- Optimized a lot of source analysis rules.
- Optimized the low level code of the UI work.
- Fixed issues that would cause the memory usage of the IDE to grow over time.
- Optimized code completion, parameter hinting, semantic highlighting.
- Optimized folder expansion in the solution pad - noticeable with folders which contain hundreds of items.
- Optimized IDE startup time for both the first run and subsequent runs.
- In general, optimized CPU usage and memory traffic for using the IDE.
- Improved: We have updated the identity service for use on systems behind a proxy. This will get the authentication details from the keychain or prompt for them. If you have been having issues signing in previously please try again and send us any feedback you have so that we continue to improve support for proxies.
- Fixed: Constraint Priority displays 0 in Properties pad; cannot be set from Designer pop-up.
- Fixed: Add the ability to specify the Platform Target for F# projects.
- Fixed: Unused namespaces code issue doesn't handle FSharp.Core namespaces correctly.
- Fixed: Many "New file" dialogs/strings are unlocalized.
- Fixed: "New Solution" dialogs are unlocalized.
- Fixed: Text is truncated in the "Configure your new Single View App" dialog.
- Fixed: Nuget Wizard tooltip is showing xml character reference '''.
- Fixed: Updater tooltip is empty when updates are paused.
- Fixed: Update git repo on VSTS fails with "null username or password".
- Fixed: Refactoring for the "nameof" scenario on first use is wrong.
- Fixed: Welcome page keeps losing my recent project when there are many recent projects.
- Fixed: iOS Build error if container app has device-specific builds enabled, while the extension does not.
- Fixed: Syntax Highlighting is not present with C#6 string interpolation for local variables.
- Fixed: In some cases, users are unable to launch Xamarin Inspector.
- Fixed: Getting Warnings while building the Native app (and iOS) in release mode.
- Fixed: .NET Core Class Library targets .NET Standard instead of netcoreapp.
- Fixed: IDE crashes when adding an image (.png or .jpg) to an iOS Storyboard.
- Fixed: Adding all Google Play Services packages fails with "System.AggregateException: One or more errors occurred. ---> System.ArgumentNullException: Value cannot be null.v Parameter name: packageIdentity.Version".
- Fixed: Quick Fix right-click submenu gets stuck up on "Loading...".
- Fixed: The file browser is not displaying SDK Location when clicking “…” file explorer option in Locations tab of the Android SDK Manager.
- Fixed: F# .NET Core projects do not compile.
- Fixed: Logging in to MS Account prompts for credentials to access proxy server graph.windows.net.
- Fixed: Deadlock in Find References and "Find Derived Types" for some F# projects.
- Fixed: Null Reference Exception when trying to add a new iOS account in Visual Studio for Mac.
- Fixed: Adding .NET Standard project to existing solution/directory structure rewrites/reformats all source code on disk.
- Removes a requirement to have a specific .NET Core version (preview 2) installed to use .NET Core 2.0. Later previews and .NET Core RTW are now supported.