Microsoft Build has always been a time when we deliver a wealth of developer-focused announcements. It’s an opportunity to share our vision for developer experiences across mobile, AR/VR, cloud, web, desktop, IoT and AI. This year, I’m excited to have brought this vision to life with more than a few exciting announcements:
The fix for the file save issue is now available in Visual Studio 2017 for Mac version 7.6 Preview 4 (7.6.0.2003). If you'd like to try it out, you can access it by changing the Update Channel under Visual Studio > Check for Updates. At the same time VS for Mac 7.4 was announced, Microsoft shipped Visual Studio 2017 15.6, with improved solution load performance topping a list of new functionality. More details about what's new in VS for Mac 7.4 can be found in our earlier coverage of a preview release.
For an overview of announcements across the company, check out Scott Guthrie’s blog post; but for a round-up of Visual Studio and .NET headlines, read on.
.NET Core 2.1 RC
As of today, .NET Core 2.1 Release Candidate (RC) is available with a “Go-Live” license to use in production. .NET Core 2.1 improves on previous releases with hard-won performance gains and many new features:
- ASP.NET Core SignalR. Developers have been using SignalR to build real-time web communication solutions since 2013 on the .NET Framework. The stack has been streamlined and improved to run on the cross-platform and higher performance .NET Core runtime. We also released SignalR as an Azure service.
- ASP.NET Core web platform enhancements including support for Razor UI in class libraries, improvements in building WebAPIs, security enhancements, a new Identity UI library and HttpClientFactory.
- Entity Framework Core 2.1 introduces significant capabilities like lazy loading, data seeding, value conversions, query types, and GroupBy translation.
- .NET Core 2.1 significantly improves build & runtime performance. It also introduces a new deployment and extensibility model for global tools.
- ASP.NET Core 2.1 is more than 15% faster than version 2.0. This means that when ASP.NET Core is released, it will top the TechEmpower benchmarks as the fastest mainstream web framework on the planet.
Of course, .NET Core remains free, cross-platform, and open source – just as it has been since 2014.
Learn more about .NET Core 2.1 RC.
Future of Windows Desktop Development
While we’re excited to release .NET Core 2.1 RC, we’re not stopping there. Today, we introduced the roadmap for .NET Core 3, which brings desktop development to our open source .NET stack. We are adding Windows Presentation Foundation (WPF) and Windows Forms on top of .NET Core. As always, developers building Universal Windows Platform apps will also continue to benefit from all the .NET Core improvements.
.NET Core 3.0 will enable Windows desktop apps use a globally installed .NET, or an app local copy, or build a single .EXE which includes .NET. Thus, .NET apps will no longer be impacted by system-wide updates. More importantly, this will allow us to make improvements to WPF and Windows Forms that we previously could not have done with .NET Framework without risking compatibility to existing apps
With .NET Core 3.0, developers will have the ability to share and easily integrate UI controls across all the major Windows desktop frameworks. You’ll be able to incorporate whatever UI controls make the most sense for your scenario, or even take a phased migration approach to modernizing your app’s UI. Developers will be able to seamlessly integrate almost all the Windows 10 API surface area into their .NET apps such as Cortana, Windows Hello, Windows ML, Rome, and more. And developers will be able to take advantage of the performance improvements and new API’s in .NET Core.
Developers targeting .NET Framework 4.8, the next version of .NET Framework, will also benefit from the improvements we plan to make such as the new Edge-based WebView control that they can host inside their apps, with more controls planned. And support for XAML Islands bringing UWP UI into existing applications.
This roadmap represents a significant investment in Windows desktop development by empowering developers to adopt the latest innovations in Windows 10 and .NET Core in their WPF and Windows Forms apps.
Visual Studio 2017, version 15.7
Our flagship IDE, Visual Studio, received a significant upgrade today with the announcement of Visual Studio 2017 version 15.7. John Montgomery’s blog post has a full run-down of all the new capabilities, but some of the more significant headlines include:
- Cloud development: You’ll find several improvements to the project scaffolding and unit testing. Additionally, you can publish Helm charts directly to Azure Kubernetes Service (AKS). You can now also directly publish .NET applications to Kubernetes containers. For your ASP.NET and ASP.NET Core applications, you can configure the Key Vault connected service directly from the IDE.
- Debugging: IntelliTrace’s new step-back debugging, first shipped in Visual Studio 2017 version 15.5, is now available for .NET Core applications. The feature automatically takes a snapshot of your application on each breakpoint and debugger step so you can step “back in time” to view previous application states.
- MSVC C++ 17 conformance: Today, we are happy to announce we have reached full C++ 17 conformance in MSVC with Visual Studio 2017 version 15.7. We also added ClangFormat support for C++ developers in the IDE. Developers can use ClangFormat to automatically style and format your code as you type, in a way that can be enforced across your development team.
- Python: This release contains an opt-in preview of the Python debugger based on the popular open source pydevd debug engine, offering improved performance for many debugging scenarios.
- iOS and Android mobile development with Xamarin: The XAML editing experience has been greatly improved with full IntelliSense support. iOS devices can be provisioned for development with a single click, saving developers a lot of time and steps. Android and iOS project templates have been re-written to use the latest modern navigation patterns and are now better organized for improved discoverability.
Visual Studio for Mac, version 7.5
Visual Studio 2017 wasn’t the only IDE to get an update. Today, we’re announcing Visual Studio for Mac version 7.5. This release includes bug fixes, performance improvements, and several new features:
- New editors for Razor, JavaScript, and TypeScript for building web projects
- Updated UI and templates for building serverless solutions with Azure Functions and .NET Core
- .NET Standard Library projects are now a fully supported option for sharing code between platforms when building Xamarin.Forms solutions.
- Preview support for Team Foundation Version Control (TFVC) in Team Foundation Server (TFS) and Visual Studio Team Services (VSTS) has arrived addressing one of our top UserVoice requests. Developers now have the option to use the existing Git source control integration or the new TFVC integration to manage their code.
Xamarin.Forms 3.0 General Availability
Today, we’re announcing immediate availability of Xamarin.Forms 3.0. Xamarin.Forms 3.0 delivers improved stability, faster performance, and new capabilities aimed at making it easier for you to create beautiful apps that work on Android, iOS, macOS, and Windows devices.
Xamarin.Forms 3.0 now builds with .NET Standard 2.0 using multi-targeting, while still maintaining support for PCL profiles and other .NET Standard versions. Projects load much faster when you use .NET Standard project types.
Xamarin.Forms 3.0 also includes a strong focus on developer productivity. Many developers are already familiar with the Visual State Manager already found in XAML for UWP and WPF. It’s now available for Xamarin.Forms, too. We’ve also heard from many ASP.NET developers who can build amazing layouts for the web using Flexbox and CSS. To empower these developers to build equally impressive layouts on mobile, we’ve added two features to Xamarin.Forms: FlexLayout and CSS. Xamarin.Forms 3.0 introduces both features without compromising the existing XAML experience desktop developers have come to know and love. Finally, because Xamarin apps are deployed globally, we also included right-to-left language support and many quality improvements in the 3.0 release.
Visual Studio Live Share Public Preview
Today, we announced the public preview of Visual Studio Live Share. Now any developer can use Live Share to collaborate in real-time with other developers, with instant bi-directional collaboration directly from their existing tools like Visual Studio 2017 and Visual Studio Code. With Visual Studio Live Share:
- It doesn’t matter if the developer sharing doesn’t use the same editor or have the same OS as you; join a Live Share session from your own development environment. No need to install project- specific dependencies or configure runtimes. You’ll view the project in your development tool, retaining all your customizations and themes.
- Each team member in a Live Share session can separately open files, navigate, edit, and refactor code. Your changes are instantly reflected in your teammate’s editor. You can quickly jump to a teammate’s location and see their cursor as they make edits or pin to follow their actions. Want to focus their attention? Highlight a piece of code and it will highlight on their screen as well.
- Use Live Share with any language on any application pattern, including serverless, cloud native, and IoT development. At Connect() 2017, we showed Live Share working with JavaScript and Node.js. Today, Live Share supports nearly every language supported by your development tool, including C#, Python, Java, Go, C++, and
- Full-context sharing – Use Live Share to collaborate across all parts of your development workflow: co-editing, shared debugging, shared terminals, and shared servers (ports).
Visual Studio IntelliCode
Visual Studio IntelliCode is a new capability that enhances everyday software development with the power of AI. Today, IntelliCode provides intelligent suggestions to improve developer productivity and code quality in the tool that developers love, Visual Studio. Our vision is to apply AI to empower developers across the entire development lifecycle.
At Build, we shared a sneak peak of IntelliCode, showing how it uses AI to deliver better context-aware code completions, guide developers to code to the patterns and styles of their team, find difficult-to-catch code issues, and focus code reviews on areas that really matter.
Developers can sign up for news and a future private preview, as well as gain access to an experimental extension at http://aka.ms/intellicode
Send us Your Feedback
Our developer tools and services are shaped by your feedback, so please let us know what you think. To download, install and read documentation for all today’s announcements, go to:
If you have any trouble, you can report a problem from inside the IDE on both Visual Studio and Visual Studio for Mac.
To track issues, ask questions and find answers, explore the Visual Studio Developer Community. Or, to engage with our team and other Visual Studio developers in real-time chat, try our new Gitter community (requires GitHub account). We welcome your product suggestions through UserVoice. And, should you need it, you can also get free installation help through Live Chat Support.
Finally, don’t forget that we have three full days of announcements, deep dives, and developer interviews to share. You can live-stream or watch on-demand video later from the Microsoft Build website.
Happy coding.
-->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.8
Visual Studio 2017 for Mac version 7.8 Releases
- May 13, 2019 – Visual Studio 2017 for Mac version 7.8.4
- March 12, 2019 – Visual Studio 2017 for Mac version 7.8.3
- February 28, 2019 – Visual Studio 2017 for Mac version 7.8.2
- February 22, 2019 – Visual Studio 2017 for Mac version 7.8.1
- February 20, 2019 – Visual Studio 2017 for Mac version 7.8
Release Highlights
This release focuses on improving the quality in Visual Studio for Mac through bug fixes, performance improvements, and reliability improvements.
We also updated the version of NuGet to 4.8, .NET Core SDK to 2.1.504, and .NET Core Runtime 2.1.8
Visual Studio 2017 for Mac version 7.8 (7.8.0.1624)
released February 20, 2019
Shell
- 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 Visual Studio for Mac would fail to track file changes for files in certain folders.
- 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 adding a new folder to a project does not allow instant renaming.
- We fixed an issue where Start Debugging after Start without Debugging results in an exception for ASP.Net projects.
- We fixed a performance issue with build output search.
- The Run Item command on the Solution Explorer has been renamed to Run Project.
- We fixed an issue where the welcome page is shown when loading a solution from finder.
.NET Core
- We updated to .NET Core 2.1.8 to include a security update.
- We fixed an issue where the create button doesn't create new project for .NET Core 3.0 preview 2.
- We fixed an issue where .NET Core 3.0 can be selected in the New Project dialog when it is not supported.
- We removed the VB.NET option from .NET Core projects.
ASP.NET Core
- We fixed an issue where the Folder profile would be created with 'Default' configuration instead of 'Release'.
Web Tools
- We fixed an issue where Publish to Azure creates a profile with the wrong name.
- We fixed an issue where application arguments are not passed to the Azure Functions host.
- We added the following additional Azure Functions templates
- CosmosDB trigger
- EventHub trigger
- IoT Hub trigger
- SendGrid trigger
- ServiceBus Queue trigger
- ServiceBus Topic trigger
- We fixed an issue where it was not possible to publish to Azure API App instances.
Xamarin
- We updated the Xamarin Test Cloud agent NuGet version.
- We fixed an issue where the View Archives command would appear in .NET Core projects.
Xamarin.Forms
- IntelliSense in Xamarin.Forms XAML files for FontFamily is now available.
Designers
- We fixed an issue where the toolbox regressed Android designer usage.
- We fixed an issue when attempting to drag and drop controls to iOS storyboards from the Tool Box after searching for controls does not work.
Xamarin.Android
- We fixed an issue where the JDK notification was shown on the welcome page, even for non-Android projects.
- 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 the Android resource update could occur at the same time as a build which could then cause build issues.
- We fixed an issue where Visual Studio for Mac would fail to upload APK to Acer Chromebook R11.
- 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
AndroidManifest
in specific build configurations.. - We fixed an issue where opening the Report A Problem dialog also displays 'Install JDK' dialog.
- We fixed an issue where the Google Play SDK warning is shown even when publishing Ad-Hoc.
Visual Studio Community For Mac
Xamarin.iOS
- It is now possible to choose .pdf files for image assets that do not support vector images.
- We fixed an issue where Visual Studio for Mac erroneously indicates that a Xamarin.Mac property is unavailable.
- We fixed an issue where it is not possible to choose devices for named colors in the asset catalog.
- We fixed an issue where the iOS simulator is no longer brought to front when starting a debug session.
- 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.
Xamarin.Mac
- We fixed an issue where .xib templates seem to need
customObjectInstantitationMethod='direct'
added. - 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.
Code Editor
- We fixed an issue where the code fix preview window is too small.
- We fixed an issue where error squiggles were not up to date.
- We fixed an issue where the editor would freeze while typing
- We fixed an issue where Changing the tab would not allow you to search a file
- We fixed an issue where Using statement indenting is incorrect.
- We fixed an issue where Roslyn throws a fatal exception (System.ArgumentOutOfRangeException).
- We fixed an issue where formatting of parameters across multiple lines is incorrect.
- We fixed an issue where the constructor generator would cause Visual Studio for Mac to crash.
- We fixed an issue where smart semicolon placement causes incorrect semicolon placement.
- We fixed an issue where typing can be slow in large files when accessibility is enabled.
- We fixed an issue where a fatal error can occur when trying to navigate inside the editor using VoiceOver.
- We fixed an issue where the caret location in quick fix margin is incorrect.
- We fixed a performance issue where indent correcting 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 code suggestion does the wrong thing when
(
is pressed after a stray arrow key.
NuGet
- We fixed an issue where Visual Studio for Mac crashes after 'Could not add packages' error.
- We updated the version of NuGet to 4.8.
- 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 a set of issues with NuGet:
- problem while restoring NuGet packages which don't have stable version.
- The VS4Mac bundle nuget version is too old: 4.3.1.
- Referencing packages conditionally using variable does not work correctly.
- Xamarin.Forms app with multi target framework library referenced fail to build.
- Visual Studio Mac Csproj build not support Item contidion.
- Support conditional NuGet PackageReferences in multi-targeting projects.
- Show per-framework dependencies when multi-targeting.
- VS cannot build F# dotnet core solution.
- Nuget restore ignore build targets.
- NuGet restores the wrong version of Microsoft.AspNetCore.App.
Debugger
- We fixed an issue where the debugger would fail when running on an external console on Mojave.
Test Tools
- 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 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 the unit test integration in the editor does not properly trigger test cases.
- We fixed an issue that could cause xunit to fail to restore.
F#
- We fixed an issue where open statements for F# must be manually added when pasting/writing code.
- We fixed an issue where new F# projects shows IntelliSense errors.
- We fixed an issue for F# projects where Visual Studio for Mac overwrites the project GUID to be lowercase instead of uppercase.
Project System
- We fixed an issue where the 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 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.
Assembly Browser
- We fixed an issue where the Assembly Browser shows the wrong icon for properties.
- We fixed an issue where
System.DayOfWeek
enum (Wednesday
) does not appear to be assigned a value.
Accessibility
- 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.
Other
- 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 is not remembering settings.
- We fixed an issue where Checking for updates can result in multiple prompts to sign in.
Visual Studio 2017 for Mac version 7.8.1.4
released February 22, 2019
- We fixed an issue where Visual Studio for Mac becomes unresponsive when selecting two column view.
Visual Studio 2017 for Mac version 7.8.2.1
released February 28, 2019
- We fixed an issue where Debugger features sometimes don't work as expected with Unity.
Install Visual Studio For Mac
Visual Studio 2017 for Mac version 7.8.3.2
released March 12, 2019
- This release contains an updated 4.8 NuGet Client, which in turn closes a NuGet Client vulnerability.
- We fixed an issue where Using Git to publish an existing project to a new remote repository was not working.
- We fixed an issue where Git remote operations were failing in Visual Studio for Mac:.
- We fixed an issue where Tooltips not being shown for F# solutions.
- We fixed an issue where The Report a Problem dialog crashes Visual Studio for Mac when entering details.
- We fixed an issue where Visual Studio for Mac crashes while using Report a Problem if the debugger connection is lost.
- We fixed an issue where Two sign in popup windows would show if you weren't signed in and tried to Report a Problem.
- We fixed an issue causing warnings about missing icons to show up in the log files when using Report a Problem.
- We fixed an issue preventing build messages from displaying in the Build Output window after building Docker Compose projects.
Visual Studio 2017 for Mac version 7.8.4.1
released May 13, 2019
- This release fixes an issue where (Visual Studio for Mac 7.8.3 crashes after loading a second solution)[https://developercommunity.visualstudio.com/content/problem/509716/visual-studio-783-build2-crashes-after-loading-a-s.html].
Feedback
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.
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
You can view prior versions of Visual Studio 2017 for Mac release notes on the Release notes history page.