News

Visual Studio 2019 for Mac 8.3 'In the Endgame'

With the big .NET Core 3.0 milestone coming up in two weeks, Microsoft is finishing off its tooling updates, including the recently announced Visual Studio 2019 for Mac version 8.3 Preview 3.

"We're in the endgame of finishing the Visual Studio for Mac 8.3 release," said Jordan Matthiesen, senior program manager, in an announcement post.

In v8.3, the dev team is focusing on top themes gleaned from customer feedback, including:

  • Improving the ASP.NET Core developer workflow (including brand-new Web editors).
  • Enabling the development of libraries targeting multiple .NET frameworks.

That first item addresses numerous developer complaints about persistent performance and reliability issues in the IDE, especially the excruciatingly slow C# editor, whose original core internals were replaced by those of Visual Studio for Windows.

Following a revamped C# editor and a new XAML editor introduced in earlier versions, VS for Mac 8.3 is updating all the Web editors.

VS Mac JavaScript Editor in Action
[Click on image for larger, animated GIF view.] VS Mac JavaScript Editor in Action (source: Microsoft).

"The new Web editors are based on the same native UI as the C# and XAML editors and provide all the advanced features recently introduced to Visual Studio for Mac, such as multi-caret editing, RTL support and native input support," Matthiesen said. "In addition to these high–level editor features, the new Web experience is also powered by the same core as Visual Studio on Windows, so you can expect the same language service features that make Visual Studio such a productive IDE. These language services provide vital features, such as IntelliSense as well as code formatting, syntax highlighting and navigation support."

The second major item of focus, the multi-targeting functionality, addresses scenarios where .NET Standard can't be used to add support for multiple platforms, requiring an alternative method of using APIs for that.

"In that case," Matthiesen said, "the best solution is to use multi-targeting to build for multiple .NET frameworks. Recently, we included support for working on projects that support multi-targeting, and in Preview 3 we've continued to improve upon that experience. When editing code in one of these projects, you can use a Target Framework drop down at the top of the editor window to focus your editing experience on a specific target framework."

The team also added support for NuGet solution-level package management functionality to help keep packages updated across multiple projects within a solution. "With the improvements we made in this area, now it's easier to consolidate to a single version of packages across the solution," Matthiesen said.

Pointing to the VS for Mac roadmap, Matthiesen said more work will be done to improve the code editors. The roadmap says v8.3 has preview support for the .NET Core 3.0 SDK.

.NET Core 3.0 is set to be released during Microsoft's online .NET Conf to be held Sept. 23-25.

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube