Visual Studio For Mac 7

Posted By admin  On 04.03.21



  1. Visual Studio For Mac 7 Cheese
  2. Visual Studio For Mac 7.7
  3. Visual Studio For Mac 8.6
  4. Visual Studio Mac Vs Windows
  5. Visual Studio For Mac 7.8
-->

Visual Studio for Mac version 7.5 now supports.NET Core 2.1 RC. Major improvements include faster build performance, better compatibility with.NET Framework, and closing gaps in both. In Visual Studio 2017 for Mac (version 7.7), we will enable the Roslyn-powered brace completion and indentation engine which helps improve your efficiency and productivity while writing C# code. We’re also making our quick fixes and code action more discoverable by introducing a light-bulb experience.

Per iniziare a sviluppare app .NET native e multipiattaforma in macOS, installare Visual Studio 2019 per Mac seguendo i passaggi indicati di seguito.To start developing native, cross-platform .NET apps on macOS, install Visual Studio 2019 for Mac following the steps below.

RequisitiRequirements

  • Mac con macOS High Sierra 10.13 o versione successiva.A Mac with macOS High Sierra 10.13 or above.

Per compilare app Xamarin per iOS o macOS, è anche necessario:To build Xamarin apps for iOS or macOS, you'll also need:

  • Xcode 10.0 o versione successiva.Xcode 10.0 or above.È in genere consigliabile usare la versione stabile più recente.The latest stable version is usually recommended.
  • ID Apple.An Apple ID.Se non si ha ancora un ID Apple, è possibile crearne uno nuovo all'indirizzo https://appleid.apple.com.If you don't have an Apple ID already you can create a new one at https://appleid.apple.com.L'ID Apple è necessario per installare Xcode e accedervi.It's necessary to have an Apple ID for installing and signing into Xcode.

Istruzioni per l'installazioneInstallation instructions

  1. Scaricare il programma di installazione dalla pagina di download di Visual Studio per Mac.Download the installer from the Visual Studio for Mac download page.

  2. Al termine del download, fare clic su VisualStudioforMacInstaller.dmg per montare il programma di installazione, quindi eseguirlo facendo doppio clic sul logo a forma di freccia:Once the download is complete, click the VisualStudioforMacInstaller.dmg to mount the installer, then run it by double-clicking the arrow logo:

  3. È possibile che venga visualizzato un avviso relativo al download dell'applicazione da Internet.You may be presented with a warning about the application being downloaded from the Internet.Fare clic su Apri.Click Open.

  4. Attendere mentre il programma di installazione verifica il sistema:Wait while the installer checks your system:

  5. Verrà visualizzato un avviso che chiede di accettare le condizioni di licenza e l'informativa sulla privacy.An alert will appear asking you to acknowledge the privacy and license terms.Seguire i collegamenti per leggerle e quindi premere Continua se si accettano:Follow the links to read them, then press Continue if you agree:

  6. Verrà visualizzato l'elenco dei carichi di lavoro disponibili.The list of available workloads is displayed.Selezionare i componenti da usare:Select the components you wish to use:

    Se non si desidera installare tutte le piattaforme, usare la guida seguente per decidere quali piattaforme installare:If you do not wish to install all platforms, use the guide below to help you decide which platforms to install:

    Tipo di appType of AppDestinazioneTargetSelezioneSelectionNoteNotes
    App che usano NovellApps Using XamarinXamarin.FormsXamarin.FormsSelezionare le piattaforme Android e iOSSelect Android and iOS platformsÈ necessario installare XcodeYou will need to install Xcode
    Solo iOSiOS onlySelezionare la piattaforma iOSSelect iOS platformÈ necessario installare XcodeYou will need to install Xcode
    Solo AndroidAndroid onlySeleziona piattaforma AndroidSelect Android platformSi noti che è necessario selezionare anche le dipendenze rilevantiNote that you should also select the relevant dependencies
    Solo MacMac onlySeleziona piattaforma MacOS (Cocoa)Select macOS (Cocoa) platformÈ necessario installare XcodeYou will need to install Xcode
    Applicazioni .NET Core.NET Core applicationsSelezionare piattaforma .NET Core .Select .NET Core platform.
    Applicazioni Web ASP.NET CoreASP.NET Core Web ApplicationsSelezionare piattaforma .NET Core .Select .NET Core platform.
    Funzioni di AzureAzure FunctionsSelezionare piattaforma .NET Core .Select .NET Core platform.
    Sviluppo di giochi Unity multipiattaformaCross-platform Unity Game DevelopmentNon è necessario installare altre piattaforme oltre Visual Studio per Mac.No additional platforms need to be installed beyond Visual Studio for Mac.Fare riferimento alla guida all'installazione di Unity per altre informazioni sull'installazione dell'estensione di Unity.Refer to the Unity setup guide for more information on installing the Unity extension.

  7. Dopo aver effettuato le selezioni, premere il pulsante Installa.After you have made your selections, press the Install button.

  8. Il programma di installazione visualizzerà lo stato di avanzamento del download e dell'installazione di Visual Studio per Mac e dei carichi di lavoro selezionati.The installer will display progress as it downloads and installs Visual Studio for Mac and the selected workloads.Verrà richiesto di immettere la password per concedere i privilegi necessari per l'installazione:You will be prompted to enter your password to grant the privileges necessary for installation.:

  9. Una volta installato, Visual Studio per Mac chiederà di personalizzare l'installazione effettuando l'accesso e selezionando i tasti di scelta rapida che si vuole usare:Once installed, Visual Studio for Mac will prompt you to personalize your installation by signing in and selecting the key bindings that you'd like to use:

Se si riscontrano problemi di rete durante l'installazione in un ambiente aziendale, rivedere le istruzioni per l'installazione di Visual Studio per Mac protetto da un firewall o un proxy.If you have network trouble while installing in a corporate environment, review the installing behind a firewall or proxy instructions.

Altre informazioni sulle modifiche sono disponibili nelle note sulla versione.Learn more about the changes in the release notes.

Nota

Se si è scelto di non installare una piattaforma o uno strumento durante l'installazione originale (deselezionandolo nel passaggio 6), è necessario eseguire di nuovo il programma di installazione se si vogliono aggiungere i componenti in un secondo momento.If you chose not to install a platform or tool during the original installation (by unselecting it in step #6), you must run the installer again if you wish to add the components later.

Installare Visual Studio per Mac protetto da un firewall o un server proxyInstall Visual Studio for Mac behind a firewall or proxy server

Per installare Visual Studio per Mac protetto da un firewall, determinati endpoint devono essere resi accessibili per consentire i download degli strumenti e degli aggiornamenti necessari per il software.To install Visual Studio for Mac behind a firewall, certain endpoints must be made accessible in order to allow downloads of the required tools and updates for your software.

Configurare la rete per consentire l'accesso alle posizioni seguenti:Configure your network to allow access to the following locations:

Passaggi successiviNext steps

L'installazione di Visual Studio per Mac consente di iniziare a scrivere codice per le app.Installing Visual Studio for Mac allows you to start writing code for your apps.Le guide seguenti vengono fornite per eseguire i passaggi successivi di scrittura e distribuzione dei progetti.The following guides are provided to guide you through the next steps of writing and deploying your projects.

iOSiOS

  1. Provisioning di dispositivi (per eseguire l'applicazione nel dispositivo).Device Provisioning(To run your application on device).

AndroidAndroid

app .NET core, app Web ASP.NET Core, sviluppo di giochi Unity.NET Core apps, ASP.NET Core web apps, Unity game development

Per altri carichi di lavoro, vedere la pagina Carichi di lavoro.For other Workloads, refer to the Workloads page.

Video correlatoRelated Video

Vedi ancheSee also

-->

Developer Community |System Requirements |Compatibility |Distributable Code |Xamarin |Blogs |Servicing |

Click the button to download the latest version of Visual Studio 2017 for Mac. For instructions on setup and install, see the Setup and Install Visual Studio for Mac documentation.

To learn more about Visual Studio 2017 for Mac, see Mac System Requirements and Mac Platform Targeting and Compatibility.

To learn more about other related downloads, see the Downloads page.

What's New in 7.7

Visual Studio 2017 for Mac version 7.7 Releases

  • January 30, 2019 – Visual Studio 2017 for Mac version 7.7.4
  • January 16, 2019 – Visual Studio 2017 for Mac version 7.7.3
  • December 17, 2018 – Visual Studio 2017 for Mac version 7.7.2
  • December 6, 2018 – Visual Studio 2017 for Mac version 7.7.1
  • November 28, 2018 – Visual Studio 2017 for Mac version 7.7

Release Highlights

  • Visual Studio for Mac now supports .NET Core 2.2.
  • We added new icons to show you when quick fixes are available.
  • We now support Publish to folder for ASP.NET Core projects.
  • NuGet has been updated to version 4.8.

Known Issues

Refer to the Known Issues section.

Details of What's New in 7.7

Visual Studio 2017 for Mac version 7.7

released November 28, 2018

New Features in 7.7

  • Visual Studio for Mac now supports .NET Core 2.2.
  • We added new icons to show you when quick fixes are available.
  • We now support Publish to folder for ASP.NET Core projects.
  • NuGet has been updated to version 4.7.

Quick fix improvements

Quick fixes can now be applied by using the light bulb or screwdriver icons in the C# editor, or by pressing Option+Enter when your cursor is on a line of code for which an action is available. You will see an error light bulb if there is a red squiggle indicating an error, and Visual Studio for Mac has a fix available for that error.

Publish to folder option for ASP.NET Core projects

When developing ASP.NET Core applications, there are many different options for hosting your application.In previous releases we supported publishing your ASP.NET Core applications to Azure App Services. In this release we are adding the ability to publish ASP.NET Core applications to a folder.After publishing your application to a folder, you can then transfer the files to the remote server, which will host your applications.When you use the new Folder Publish feature, it will automatically create a Publish Profile (.pubxml file in PropertiesPublishProfiles). These profiles can be used in either Visual Studio for Mac, Visual Studio 2017 (Windows) or from the command line with dotnet build (or MSBuild).

Code Editor

For this release we fixed the following Code Editor issues:

  • Fixed an issue where incorrect colors were displayed when dragging a document tab.
  • Fixed an issue where Ctrl+Right and Ctrl+Left would skip too much text in the editor.
  • Fixed an issue where Cmd-click navigation sometimes gets stuck.
  • Fixed an issue where Cmd does not light up navigation for symbol under mouse
  • Fixed an issue where Breakpoints and caret location were not displayed in the scrollbar.
  • Fixed an issue where Extract Interface dialog layout would flicker.
  • Fixed an issue where 'Copy comments from base' refactoring would suggest including comments from the base class library.
  • Fixed an issue where it was not possible to see the mouse over content when using the keyboard.
  • Fixed an issue where CopyCommentsFromBaseCodeRefactoringProviderwould throw an XML parse exception.
  • Fixed an issue where an error in document creation causes a cascade of errors leading to a crash.
  • Fixed an issue where the text Editor outdents to hard left instead of going back an indent level.
  • Fixed an issue where the editor would not render whitespace marks for virtual space.
  • Fixed an issue where the regex completion provider would crash.
  • Fixed an issue where C# completion improperly escapes within @ strings.
  • Fixed an issue where code completion would incorrectly insert code.
  • Fixed an issue where the IntelliSense window would obscuring code when 'Show function type signatures' is enabled.
  • Fixed an issue where Minimap could be turned off.
  • Fixed an issue where Razor completion would not commit the change if the caret is immediately followed by '}'.
  • Fixed an issue where renaming a class would ask to reload the file.
  • Fixed an issue where '[TestCaseSource ('xzy')]' was not seen as a test in the text editor.
  • Fixed an issue where Alt-shift-left/right would not extend the selection.
  • Fixed an issue where an error would be logged for the Text Mate text editor extension.
  • Fixed an issue where it was not possible to configure tabs in XAML files with an EditorConfig file.
  • Fixed an issue where the Tab size in the editor was wrong.
  • We aligned quote matching behavior to match Visual Studio.
  • We fixed an issue where Cut and Paste would not convert @' and ' formatting automatically.
  • We fixed an issue where code snippets would fail to load when there is a malformed snippet.
  • We fixed an issue where the indentation in multi-line field initializers is wrong when working with arrays.
  • We fixed an issue where .editorConfig doesn't work when using .NET Core Rules.
  • We fixed an issue where C# indentation inside method is not aligning with existing code.
  • We fixed an issue where there is inconsistent indentation between VS Windows and VS Mac.
  • We fixed an issue where it is not obvious which 'fix all' is which.
  • We fixed an issue were an exception is thrown when using syntax highlighting in Visual Studio for Mac 7.6.
  • We fixed an issue where Visual Studio for Mac IntelliSense does not work correctly in version 7.6.1 (build 9).
  • We fixed an issue where Visual Studio for Mac IDE themes look wrong.
  • We fixed an issue where deleting emoji in source file creates gray bars.
  • We fixed an issue where sorting usings does not work.
  • We fixed some editor IntelliSense/Code Generation bugs.
  • We fixed an issue where completion suggestion mode does not work as expected in collection initializers.
  • We fixed an issue where format document does not use the correct formatting settings.
  • We fixed an issue where the indentation after end of method is incorrect.
  • We fixed an issue where cut and paste is broken in the editor.
  • We fixed an issue with the Oblivion color style.
  • We fixed an issue where some C# templates do not work when invoked in the editor.
  • We fixed an issue where enabling or disabling a breakpoint opens quick fixes menu.
  • We fixed an issue where IntelliSense completion commits on ENTER when an item is soft-selected.
  • We fixed an issue where an invalid URI exception is thrown on opening file in root directory.
  • We fixed an issue where Intellisense stops working on random files.
  • We fixed an issue where fix all in file is slow and unreliable, fails silently.
  • We fixed an issue where 'CreateChangedEventCodeRefactoringProvider' encountered an error and has been disabled..
  • We fixed an issue where 'ReplacePropertyWithBackingFieldWithAutoPropertyCodeRefactoringProvider' encountered an error and has been disabled.
  • We fixed an issue where re-entering an event handler, after code generation from +=, if the corresponding method has been changed causes code generation to fire again.
  • We fixed an issue where the mouse cursor is always an arrow and Visual Studio Mac (7.4 Build 884) mouse cursor is always an arrow.
  • We fixed an issue where 'Show Invisible Characters' setting keeps being reset in 7.6.
  • We fixed an issue where it was not possible to create new files for a solution and Error creating file - Index was outside the bounds of the array, new XAML file does not include code-behind.
  • We fixed an issue where an error is thrown when creating a file - NullReferenceException: Object reference not set to an instance of an object.
  • We fixed an issue where files removed from a project are not deleted when 'Delete' is chosen.
  • We fixed an issue where NullReferenceException calling NR5CompatibiltyExtensions.GetFullName.
  • We fixed an issue where ExtractMethodCodeRefactoringProvider encountered an error and has been disabled.
  • We fixed an issue where IntelliSense stops working when creating a new file and Intellisense/Autocomplete constantly failing.
  • We fixed an issue where 'add using' writes the wrong reference down for a framework assembly.
  • We fixed an issue where 'using' imports no longer suggested in the Quick Fix menu and Quick fix does not offer to add using statement if source analysis is disabled.
  • We fixed an issue where ToAbstractVirtualNonVirtualConversionCodeRefactoringProvider fails and gets disabled.
  • We fixed an issue where you cannot save any edits to Visual Studio for Mac files onto a USB Flash Drive.
  • We fixed an issue where copy and paste sometimes fails on Visual Studio for Mac.
  • We fixed an issue where XML intellisense autocompletes too early.
  • We fixed an issue where there is no syntax highlighting for .vb files.
  • We fixed an issue where you are unable to change font colors for VB.net in Visual Studio Community 2017 for Mac.
  • We fixed an issue where the Screwdriver icon never goes away in using statements.
  • We fixed an issue where code refactoring providers would crash.
  • We fixed an issue where renaming public types would fail.
  • We fixed an issue where the code issue icon displayed as a wrench, rather than a light bulb, for removing Using directives.
  • We fixed an issue where Method level fixes show up throughout method body.
  • We fixed an issue where there is no syntax highlighting for .vb files.
  • We fixed an issue where it is not possible to change font colors for vb.net.

Shell

  • We fixed an issue where there are no tooltips on toolbar.
  • We fixed an issue where new Application Output windows are created on each run.
  • We fixed an issue where refactoring or error info bars would be shown duplicated.
  • We fixed an issue where there are shadow artifacts in Tooltips on Mojave.
  • We fixed an issue where pinned projects are no longer remaining pinned after a restart of Visual Studio for Mac.
  • We fixed an issue where application output shows nothing after clearing the console.
  • We fixed an issue where 'Application output' inside the IDE stops working once cleared.
  • We fixed an issue where the InfoBar incorrectly adds a hyphen to the end of the displayed text.

Project

  • We fixed an issue where intermittent errors would appear after creating a new .NET Core project.
  • We fixed an issue where OutputBase no longer includes the build configuration.
  • We fixed an issue where Visual Studio for Mac builds all projects instead of just the executable and dependencies only when running the project.
  • We fixed an issue where the project GUID changes when building in VS2017 vs building in Visual Studio for Mac.
  • We fixed an issue where an invalid configuration mapping error is displayed when loading an SDK-style project.
  • We fixed an issue where it is not possible to open Specflow feature file.
  • We fixed an issue where symlinked files do not have correct define constants.

Accessibility

  • We made the following accessibility improvements:

    • better contrast in the New Project Dialog
    • better contrast in the Exception dialog
    • VoiceOver improvements

  • We fixed the following issues:

    • There was a loss of focus when configuring the location of a new project.
    • We made it possible to invoke the 'Error' window and 'Visual Studio Update' window using the keyboard.
    • VoiceOver announces the text typed into password secured fields.
    • VoiceOver focus is not moving to the search results along with the keyboard focus.
    • We fixed an issue where typing can be slow in large files when accessibility is enabled.
    • Focus order is inappropriate while navigating to the tree items in the left pane of the 'Preferences' window.
    • Focus order is inappropriate while navigating in reverse order in the toolbar.
    • On hitting escape key in 'Value Visualizer' window, both the 'Value Visualizer' and 'Exception Caught' windows are getting closed.
    • Voiceover doesn't announce the name of the close button in the pop up dialogs.
    • Voiceover announces the controltype of 'General' heading in 'Choose a template for your new project' dialog inappropriately.
    • Voiceover doesn't announce the relation between each of the category and the options under it in 'Project Categories' table.

.NET Core

  • Visual Studio for Mac now supports .NET Core 2.2.
  • We added support for .NET Core projects that use explicit Sdk imports.
    For example:
    <Import Sdk='Microsoft.NET.Sdk' Project='Sdk.props' /><Import Sdk='Microsoft.NET.Sdk' Project='Sdk.targets' /><Sdk Name='Microsoft.NET.Sdk' Version='1.0.0' />
  • We fixed an issue where .NET Standard missing from the target framework list.
  • We fixed an issue where creating a new .NET Core project semi-failed.
  • We fixed an issue where possible copy paste error in .NET Core options panels.
  • We fixed an issue where, after installing .NET Core 2.2 preview, .NET Core 2.1 projects no longer build.
  • We fixed an issue where the publish menu was incorrectly available for all project types.
  • We fixed an issue where a null reference exception would be thrown when Publish to Folder for a solution is selected.

Feedback Client

  • We fixed an issue where the Feedback dialog sometimes disappears and is always visible in screenshot.

Web Tools

  • We fixed an issue where pressing Tab doesn't complete the statement in .cshtml files.
  • We fixed an issue where an error is thrown when inserting new line between <div> and </div> in HTML files.
  • We fixed an issue where tooltips do not close in Visual Studio for Mac.
  • We fixed an issue where the user could not type in .json files.
  • We display more informative error messages when new Azure app services fail to provision.
  • We fixed an issue where Visual Studio for Mac fails to debug ASP.NET Core Web App with error 'Debug/netcoreapp2.1/testing.dll file was not found. (MSB3030) (docker-compose)'.
  • We fixed an issue where the Add Docker command could fail with a NullReferenceException.
  • We fixed an issue where Visual Studio for Mac would fail to find some subscriptions.

Visual Studio For Mac 7 Cheese

NuGet

  • We fixed an issue where PackageReferences with no version were not supported.
  • We fixed an issue where Visual Studio for Mac crashes when restoring packages that have lots of SDK style projects.
  • The Update and Restore commands should be disabled for SDK NuGet for .Net Core projects.

Version Control

  • Subversion support on Mac should depend on either Xcode or the CommandLineTools, not just Xcode.
  • We fixed an issue where the text on the Git credentials pop up window was formatted incorrectly.
  • We fixed an issue where Visual Studio for Mac prompts for Git Credentials every time 'Update Solution' or 'Push Changes' is called.

F#

  • 'Find Reference Usages' is now supported.
  • 'Find Implementing Symbols' is now supported.
  • Fixed an issue where a fatal exception could occur when building a F# project.
  • Fixed an issue where the IDE would hang when getting extension methods for F#.

Docker

  • We fixed an issue where the run button is not working.

Xamarin

This release includes the following bug fixes and improvements for Xamarin:

Xamarin.Forms

  • We fixed an issue where the namespace for new Forms Content Page (XAML) in F# is wrong.
  • We fixed an issue where go to error / location in XAML fails.
  • We fixed an issue where Go To Error/Location in XAML would not take you to the correct location.

Xamarin.Android

  • With Visual Studio 2017 15.9 and Visual Studio for Mac 7.7, we are moving from Oracle's JDK to a lightweight distribution of Open JDK meant for mobile development. Open JDK will be offered as a component to install along with other Visual Studio for Mac updates and you will be prompted to update your JDK settings to use Open JDK once installed.
  • The Device Manager startup time has been optimized.
  • The available system images now reflect the available options for the selected manifest. This enables Android P support for the device manager when the google manifest is selected in the SDK manager.
  • The device manager no longer relies on the JAVA_HOME environment variable being set and it is exported it for processes that require it.
  • Fixed an issue where AVD Rename would crash the app for the custom ANDROID_AVD_HOME case.
  • Fixed an issue where the Device Manager would not indicate there had been system image installation failure.
  • Fixed an issue where jarsigner would be used instead of apksigner.
  • Fixed an issue where it would not be possible to run an Android app in the emulator.
  • Building an Android project when the Java SDK cannot be found is correctly reported as a build error instead of reporting that the Android SDK cannot be found.
  • Wording and behavior made consistent with Visual Studio on Windows regarding how we handle target framework, minimum and target Android versions.
  • The target framework of the project is now controlled more explicitly, first by <uses-sdk /> in AndroidManifest.xml element if it contains the targetSdkVersion property, followed by the project's TargetFrameworkVersion. Visual Studio for Mac will migrate projects to remove AndroidUseLatestPlatformSdk if it exists. It will also update AndroidManifest.xml to add <uses-sdk /> if it is missing.
  • When publishing to Google Play, we now warn if your app has a targetSdkVersion less than API 26.
  • We fixed an issue where the build should fail fast if target framework is not compatible with target device.
  • We fixed an issue where Cannot enable 'INTERNET' permission on AndroidManifest.xml dialog with F# projects.
  • We fixed an issue where Visual Studio for Mac was reporting Execution failed instead of the informing that the emulator was corrupted.
  • We fixed an issue where custom commands do not execute when archiving Android app.
  • We fixed an issue where the user is not prompted to install Android APIs above 25 if they are not installed.
  • armeabi ABI option has been removed now that it is no longer a supported ABI architecture.
  • The Minimum Android version and Target Android version selectors in the Android Application settings no longer provide 'Automatic' options. These often resulted in the AndroidManifest.xml file missing minSdkVersion and targetSdkVersion attributes. A manifest missing these values is not practical and additionally can cause issues when publishing to the Play Store.
  • We fixed an issue where it is not possible to create a service run configuration.
  • We fixed an issue where the binding template of Android Library contains a typo.
  • We fixed an issue where trying to upload an ANDROID release to GooglePlay fails with 'Version 38 of this app cannot be downloaded by any devices as they will all receive APKs with higher version codes.'.
  • We fixed an issue where opening Report A Problem also displays 'install JDK' dialog.
  • We fixed an issue where it is not possible to debug a separate service in Xamarin.Android app (can't create a service run configuration).

Xamarin.iOS

This release adds support for new ARKit 2.0 asset catalog resources: ARReferenceGroup, ARReferenceImage and ARObject.

ARKit 2.0 supports 2D and 3D objects detection. ARReferenceImage is the new asset catalog type for 2D images that can be used and recognized by ARKit. Width and Height of the ARReferenceImage can be set in the asset editor so ARKit can render virtual overlays of the correct dimensions. The ARObject type takes an '.arobject' file that can be created by some ARKit samples.

We also made the following improvements:

  • We updated our CoreML support:
    • CoreML Model Viewer has been updated to display the new Custom Layers that were introduced with Xcode 10 and iOS 12.
    • CoreML code-behind generator has been updated to add more convenience methods.
  • We fixed an issue that caused random crashes - Xamarin.MacDev.MobileDeviceException: Device is invalid.
  • We fixed an issue where the iOS project properties window for image resource sets incorrect property in .csproj file.
  • We fixed an issue with migration from WatchKit to Xamarin.WatchOS.
  • Fixed an error updating an Xcode project.
  • Fixed an issue where Automatic iOS provisioning profile dialog did not have clickable links.
  • Fixed an issue where archiving would use a generic iOS device target even if a specific device is selected.
  • We added support for editing Background Modes for WatchKit Extensions.
  • We added support for CarPlay assets.
  • Added support for Metal 4v1 and 5v1 to DataSet Asset Catalog editor.
  • Added new WatchOS App Icon selectors for the new 40mm and 44mm watches.
  • Added support for Apple Watch Series 4 complications.
  • Updated the CoreML Model Viewer to display the new Custom Layers that were introduced with Xcode 10 and iOS 12.
  • Added support for the AutoFill Credential Provider entitlement.
  • Updated the CoreML code-behind generator to add more convenience methods.
  • We fixed an issue where saving of 'Optimize' metadata for stand-alone image assets in the Properties Pad.
  • We fixed an issue where enabling/disabling keychain access groups may not be persisted to the entitlements file.
  • We fixed an issue where it was not possible to set launch images for iPhone Xs Max and iPhone XR.
  • We fixed an issue where new iOS projects not being being created correctly....
  • We fixed an issue where enabling and disabling keychain access groups may not be persisted to the entitlements file.
  • When archiving a build for publishing, we make sure to build targeting a generic iOS device in case the project is configured the build to using device-specific builds.
  • When archiving a build for publishing, we make sure to save open files in accordance with IDE preferences.
  • We fixed an issue where the simulators were not sorting correctly for new iPhone XS and XR devices.
  • We now recommend installing Xcode if the version needed by Xamarin.iOS is incompatible.

Xamarin.Mac

Visual Studio For Mac 7
  • Added support for changing the .NET Framework version to use for 'Full Framework' projects. Projects are no longer limited to just .NET 4.5.
  • We fixed an issue where Visual Studio for Mac would fail to show new API levels in Minimum and Target Android version drop downs.
  • We improved the error messaging when no JDK is installed. Previously it was not obvious whether the JDK or the Android SDK was not installed.
  • We fixed an issue where Visual Studio for Mac was unable to connect to Xcode 9.2 after updating to version 7.6 (build 2190).
  • We fixed an issue where opening Mac Cocoa project storyboard failed.

Activation

  • We fixed an issue where license verification process doesn't use proxy.
  • We fixed an issue where the user is unable to log into Visual Studio for Mac.

Installer

Feature Improvements

Microsoft

We made the following improvements to the installer:

  • With Visual Studio 2017 15.9 and Visual Studio for Mac 7.7, we are moving from Oracle's JDK to a lightweight distribution of Open JDK meant for mobile development. Open JDK will be offered as a component to install along with other Visual Studio for Mac updates and you will be prompted to update your JDK settings to use Open JDK once installed.
  • We added better descriptions to the workload selection. We hope that these descriptions will make it easier for you to decide which workloads you want to install.
  • We also made some other minor changes to the workload selection screen, making things clearer and concise for our users.
  • In this release we focused a lot on improving our localization in the installer. We added localization to more branding, the splash screen, and workloads screen to make it more accessible for all users worldwide.
  • We understand that not all of our users are using Xamarin and therefore may not have any need to download Xcode. For this reason, we've moved the location of the Xcode dialog to the end of the install and will only prompt it for Xamarin users who do not have it installed (or up to date). This means that you can download Xcode while starting your development, rather than having it interrupt your install.
  • We also understand that Visual Studio for Mac users that don't use Xamarin have no need for the Xamarin Profiler. For this reason, we've removed Profiler from non-Xamarin workloads.

Bug fixes

This this release we fixed the following bugs:

  • We fixed an issue where if an Xcode update was available it would still say 'Get Xcode'. We changed this to 'Update Xcode'.
  • We fixed an issue where the Profiler is getting installed from installer even though user has not selected any Xamarin workload.
  • We fixed an issue where the Profiler is not getting installed from installer though user has selected all Xamarin workloads.
  • We fixed an issue where a Visual Studio for Mac upgrade fails to copy symlink.

Other

  • Fixed an issue where the version control Diff view would not show the correct changed text.
  • Fixed an issue where the Class pad shows compiler generated fields and constructors.
  • Fixed an issue where an error was logged when the news feed could not be retrieved.
  • Fixed an issue where the updater would not display 'Checking for updates...' until the channel was changed.
  • Fixed an issue where the Sign in button for publishing to Azure was not rendered correctly.
  • Fixed an issue where running unit tests always ran a full build.
  • Fixed an issue with running NUnit 3 tests due to a misnamed test runner application.
  • The Welcome page is no longer displayed when loading a solution from Finder.
  • We fixed an issue where the UnitTest text editor extension causes slowness in the IDE.
  • Assembly Explorer listing changes method name when hovering mouse over the method/constructor names.
  • We fixed an issue where the New Project dialog does not select a recent template by default.
  • We fixed an issue where Build project before executing unit tests was incorrectly prompting.
  • We fixed an issue where there was a stack overflow on running unit tests.
  • We fixed an issue where adding a unit test, Visual Studio for Mac will crash with a stack trace that seems to try to recursively add the unit test.
  • We fixed an issue where cannot add .bat (Windows Batch files) to projects - Visual Studio for Mac hangs indefinitely.

Visual Studio 2017 for Mac version 7.7.1.15

released December 6, 2018

This releases addresses the following issues:

  • We fixed an issue where the C# editor would invoke autocompletion when characters like '.' or '<' are typed.
  • We fixed an issue where IntelliSense completion would behave unexpectedly.
  • We fixed an issue where Visual Studio for Mac is inserting matching braces even though the Insert matching brace option is disabled.
  • We fixed an issue where a null reference exception in MainToolbarController is raised.
  • We fixed an issue where Visual Studio for Mac fails to start.
  • We fixed an issue where autogenerated docker files are faulty.
  • We fixed an issue where it was not possible to restore, view or download NuGets in Visual Studio for Mac.
  • We fixed an issue where the NuGet package manager could fail to restore packages when updating target framework.
  • We fixed an issue where the UnitTestService rebuilds tests multiple times on solution open.
  • We fixed an issue where Visual Studio for Mac could not update.

Visual Studio 2017 for Mac version 7.7.2.21

released December 17, 2018

This releases addresses the following issues:

  • We updated the version of NuGet to 4.8.
  • We fixed an issue where launching Visual Studio for Mac without any Java installed shows 2 system prompts to install Java.
  • We fixed an issue where updates to OpenJDK could interfere with updating older versions of Visual Studio for Mac.
  • We fixed an issue with the Report a Problem tool where it would fail to update the Solutions count.
  • We fixed an issue where an incorrect message is displayed when deploying to an android device with an incompatible ABI.

Visual Studio 2017 for Mac version 7.7.3.43

released January 16, 2019

This releases addresses the following issues:

  • We fixed an issue where Visual Studio for Mac doesn't remember opened files.
  • We fixed an issue where the Toolbar selector for build configuration is disabled.
  • We fixed an issue where the constructor generator would cause Visual Studio for Mac to crash.
  • We fixed an issue where the text editor unit test integration ('Unit test 'name' could not be loaded') would fail.
  • We fixed an issue where new F# projects in Visual Studio for Mac shows IntelliSense errors.
  • We fixed an issue where pasting verbatim strings removes double quotes.
  • 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 Visual Studio for Mac would fail to upload APK to Acer Chromebook R11.
  • We fixed an issue where the debugger would fail when running on an external console on Mojave.
  • We fixed an issue where unchecking the 'Organize Using > Place System directives first' setting does not save.
  • We fixed an issue where Visual Studio for Mac crashes with 'A fatal error has occurred' - 'System.NullReferenceException: at (wrapper managed-to-native) ObjCRuntime.Messaging.nuint_objc_msgSend(intptr,intptr)' at Xwt.Drawing.Image.Finalize () /external/xwt/Xwt/Xwt.Drawing/Image.cs:83 when showing NuGet license dialog.

Visual Studio For Mac 7.7

Visual Studio 2017 for Mac version 7.7.4.1

released January 30, 2019

This release fixes an issue where some users are seeing an “Error retrieving error information” message in the Visual Studio for Mac updater after updating to version 7.7.3.

After installing Visual Studio for Mac version 7.7.3, if you notice the “Error retrieving error information” message in the updater, please follow these steps:

  1. Shutdown all running instances of Visual Studio for Mac.
  2. Download the latest version of Visual Studio for Mac from here.
  3. After downloading, double-click the DMG and follow the instructions to install the product to Applications by dragging and dropping the Visual Studio for Mac logo into the Applications folder in the installer UI.
  4. Relaunch Visual Studio for Mac and bring up the Updater UI. The error message should now be gone, and you will be able to see updates to Visual Studio for Mac as they are made available in the future.

This release updates Xamarin.iOS, Xamarin.Mac, and Xamarin.Android SDKs to ensure that the versions are compatible Visual Studio 2017 version 15.9.7.

For more information on those, refer to the release notes:

Known Issues

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

  • Updater broken on all channel with Updater token could not be retrieved
  • Git push command never stops running / stop button doesn't work
  • Accessibility checkbox could not be checked for VSM on Mojave
  • NRE in package manager when updating target framework

How are we doing?

We would love to hear from you! You can report a problem through the Report a Problem option in the Visual Studio for Mac IDE, and track your feedback in the Developer Community portal. For suggesting new features you can use Suggest a Feature, these are also tracked in the Developer Community.

Visual Studio For Mac 8.6

Blogs

Take advantage of the insights and recommendations available in the Developer Tools Blogs site to keep you up-to-date on all new releases and include deep dive posts on a broad range of features.

Visual Studio 2017 for Mac Release Notes History

Visual Studio Mac Vs Windows

You can view prior versions of Visual Studio 2017 for Mac release notes on the Release notes history page.

Visual studio for mac tutorial

Visual Studio For Mac 7.8

Top of Page