Persistent performance and reliability issues in the Visual Studio for Mac IDE will be addressed by replacing most of the editor internals with code from the Visual Studio for Windows IDE. That news comes in a blog today (Oct. 16) announcing Visual Studio for Mac 2019 and a new. Performance and reliability concerns have long been a focal point for the team developing VS for Mac, which the company in 2016 as 'evolving the mobile-centric Xamarin Studio IDE into a true mobile-first, cloud-first development tool for.NET and C#, and bringing the Visual Studio development experience to the Mac.' That mobile-centric Xamarin Studio IDE was based on the open source project. Mono/Xamarin guru Miguel de Icaza described VS for Mac as being built with a series of components on top of MonoDevelop. That approach apparently wasn't enough to satisfy performance and reliability concerns raised by many developers.

In announcing Visual Studio for Mac 7.6 in August, program manager Dominic Nahous multiple reliability fixes for issues 'many of you have reported.' He also listed performance fixes, saying 'One of the top reported bugs in previous releases has been performance issues in the editor.' That bug report was titled '.'

Those fixes apparently weren't enough, as today, Unni Ravindranathan, principal program manager, said: 'Improving the typing performance and reliability is our single biggest focus area for Visual Studio 2019 for Mac. We plan to replace most of the internals of the Visual Studio for Mac editor with those from Visual Studio. Combined with the work to improve our integration of various language services, our aspiration is to bring similar levels of editor productivity from Visual Studio to Visual Studio for Mac. Finally, as a result of this work, we will also be able to address a top request from users to add Right-To-Left (RTL) support to our editor.' Other major themes for Visual Studio for Mac 2019 and the roadmap include: • Support for Team Foundation version control: 'Including support for Team Foundation Server, with both Team Foundation Version Control (TFVC) and Git as the source control mechanisms, has been one of the top requested experiences on the Mac.' • Increased productivity when working with projects: 'The C# editor in Visual Studio for Mac will be built on top of the same Roslyn backend used by Visual Studio on Windows and will see continuous improvements.'

For example, to export the ThemeFontScheme from the Active Document to a file, you can use VBA like this: Sub exportThemeFontScheme() Dim dt As Office.OfficeTheme Set dt = ActiveDocument.DocumentTheme ' Substitute your username for 'username' dt.ThemeFontScheme.Save 'Macintosh HD:Users:username:Documents:myfontscheme.xml' Set dt = Nothing End Sub You should then be able to edit that XML (e.g. Microsoft word.

Visual Studio Code is the first code editor, and first cross-platform development tool - supporting OSX, Linux, and Windows - in the Visual Studio family. At its heart, Visual Studio Code features a powerful, fast code editor great for day-to-day use. Visual Studio for Mac enables the creation of.NET Core solutions, providing the back-end services to your client solutions. Code, debug, and test these cloud services simultaneously with your client solutions for increased productivity.

•.NET Core and ASP.NET Core support: 'In Visual Studio 2019 for Mac, we will add support for.NET Core 3.0 when it becomes available in 2019. We will add more ASP.NET Core templates and template options to Visual Studio for Mac and improve the Azure publishing options.' • Xamarin support: 'In addition to continuing to make improvements to the Xamarin platform itself, we will focus on improving Android build performance and improving the reliability of deploying iOS and Android apps.' • Unity support: 'Unity now supports a.NET 4.7 and.NET Standard 2.0 profile, and we’re making sure that Visual Studio for Mac works out of the box to support those scenarios. Unity 2018.3 ships with Roslyn, the same C# compiler that is used with Visual Studio for Mac, and we’re enabling this for your IDE.'