Visual Studio 2019 for Mac Preview Release Notes
This release is not "go-live" and not intended for use on production computers or for creating production code.
To learn more about other related downloads, see the Downloads page.
What's New in 8.0 Preview
Visual Studio 2019 for Mac version 8.0 Preview Releases
- February 4, 2019 – Visual Studio 2019 for Mac version 8.0 Preview 2
- December 4, 2018 – Visual Studio 2019 for Mac version 8.0 Preview 1
- This release introduces a new getting started experience.
- .NET Core 3.0 is now supported.
- 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.
- Visual Studio for Mac 8.0 is supported side by side with Visual Studio 7.7. Due to the fact that Mono and Xamarin SDKs are shared between both versions of Visual Studio for Mac, for the best experiences, we recommend you use a minimum of Mono 5.18. and if selected, Xamarin.iOS 12.2.1, Xamarin.Android 9.1.0, and Xamarin.Mac 5.2.1.
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.
Refer to the Known Issues section.
released December 4, 2018
Please that that support for Docker is not available in this release. It will be included in an upcoming preview release. for information on using Visual Studio Unity Tools with this preview, refer to the Known Issues section.
New getting started experience
With Visual Studio for Mac version 8.0, 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 simply 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.
The following issues have also been fixed in this preview 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 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 Visual Studio for Mac loses focus when I close the project window.
- 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.
- We fixed an issue where View Archives appears in the context menu of .NET Core projects.
- 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 the Assembly Browser shows the wrong icon for properties.
- We fixed an issue where
Wednesday) does not appear to be assigned a value.
- We fixed an issue where it was not possible to publish to Azure API App instances.
- We have removed the Live Player from Visual Studio for Mac.
- We fixed an issue where the toolbox regressed Android designer usage.
- We made some improvements to the startup speed.
- We improved scrolling widget support.
- We added support for adding "standard" XML namespaces to document when a corresponding attribute is set.
- We now support escape sequences like '@', '?' and Unicode escape sequences
- Added support for PDF as an image format.
- Improved support for color spaces and color precision.
- Added support for selecting named colors from asset catalogs as the value for color properties.
- Intellisense in Xamarin.Forms XAML files for FontFamily is now available.
- 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 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 "Your project is not referencing the 'Mono.Android.Version=v8.1' framework" when AndroidUseLatestPlatformSDK is true.
- We fixed an issue where Visual Studio for Mac does not recognize
AndroidManifestin specific build configurations..
- 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 it is not possible to change the target framework version for Xamarin.Mac full on re-opening project options.
- We fixed an issue where the project options for a Mac build (classic) shows incorrect UI.
- We fixed an issue where .xib templates seem to need
- We fixed an issue where Visual Studio for Mac erroneously indicates that a Xamarin.Mac property is unavailable.
- We fixed a performance issue where the "Test Results" pane has bad performance when very large amounts of text are shown.
- 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 fixed an issue where Visual Studio for Mac is not remembering settings.
- We fixed an issue for F# projects where Visual Studio for Mac overwrites the project GUID to be lowercase instead of uppercase.
released February 4, 2019
- 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..
- There are 3 new options in Preferences allowing returning users to decide what they want to see when they re-open the IDE:
- Always show me the start window
- Load previous solution on startup
- Show empty environment
- We fixed an issue where mouse hover states do not work for the list view in the start window.
- We fixed an issue where it is not possible to remove a recent project.
- We fixed an issue where users are unable to open pads from the start window.
- We fixed an issue where the start window is not hidden when debugging an application.
- We fixed an issue where the IDE would display the start window when a project or solution file was opened via Finder.
- We fixed an issue where the start window is initially shown in one size and later resized.
- We fixed an issue where the 'Sign in' button could be clicked several times before it was apparent that the sign in progress had started.
- 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.
- 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 custom key bindings for Remove Unused and Sort (usings) don't work.
- We fixed an issue where switching from the application and returning, does not focus on the editor correctly.
- We fixed an issue where the cursor in editor window is lost when switching applications.
- We fixed an issue where focusing out/into Visual Studio changes the default focused element on the UI.
- We fixed an issue where FileSystemWatcher is not watching the correct directories.
- We fixed an issue where adding new folder to project does not allow instant renaming.
- 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 debugger would fail when running on an external console on Mojave.
- We fixed an issue where Visual Studio for Mac doesn't remember opened files.
- We fixed an issue where Toolbar selector for build configuration is disabled.
- We fixed an issue where Roslyn fatal exception (System.ArgumentOutOfRangeException).
- 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 Nuget restore ignores build targets.
- .NET Core 3.0 is now supported.
- We removed the VB.NET option from .NET Core projects.
- We fixed an issue where the incorrect ClassKit entitlement value is included in the archive when archiving for publishing.
- 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 Visual Studio for Mac would fail to upload APK to Acer Chromebook R11.
- We fixed an issue where an incorrect ABI mismatch error is shown.
- 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 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 have updated Azure Functions runtime and templates (CLI). While we try to keep the bundled CLI up to date as much as possible, they inevitably get outdated. Visual Studio for Mac can now check for updates to the CLI. Currently the check for updates is performed when creating a new Functions project.
- Visual Studio for Mac also supports Azure Functions CLI installed via HomeBrew and will choose the instance with the highest discovered version.
- We fixed an issue where Application arguments are not passed to the Azure Functions host.
- This release includes Docker support for Visual Studio for Mac 8.0.
- We fixed an issue where 64 bit unit testing is not supported.
- We fixed an issue where xUnit Fact "DisplayName" not shown in test explorer if the name has a period at the end.
- We fixed an issue where xUnit Fact "DisplayName" not shown in test explorer if the name has a period at the end.
- We fixed an issue where the text editor unit test integration ("Unit test 'name' could not be loaded") would fail.
- We've given the Visual studio for Mac a fresh look with updated icons, splash screens, and carousel screens with useful content for all developers.
- 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 clarified the text in the alert dialog when doing side by side installation.
- We fixed an issue where running Help | API Documentation, nothing launches.
- We fixed an issue where there is a possible leak of large data via AsyncOperation.
- We fixed an issue where Visual Studio for Mac fails to start.
- 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.
The following is a list of all existing known issues in Visual Studio 2019 for Mac version 8.0:
- There is an issue when attempting to drag and drop controls to iOS storyboards from the Tool Box after searching for controls. To work around this issue drag and drop without searching.
- It is not possible to create Android emulators in the Device Manager, to create a new device use the stable version of Visual Studio for Mac.
- The Unity editor support for Visual Studio 8.0 is coming soon. To workaround this limitation, move the
Visual Studio (Preview).appin Applications to another location and rename it to
Visual Studio.app. Select the new
Visual Studio.apppackage from the Unity Preferences > External Tools option in Unity. Note, you may need to hold down Command while dragging Visual Studio (Preview).app to move the app and not create a shortcut.
Visual Studio 2017 for Mac Release Notes History
You can view prior versions of Visual Studio 2017 for Mac release notes on the Release notes history page.