Are you ready for the latest version of Visual Studio 2019 for Mac? If so, version 8.7 is available for you to download today<\/a>! With this release, we\u2019ve continued to polish the existing experience, paying close attention to many of the problem areas mentioned by our users.<\/p>\n Visual Studio for Mac now includes support for generating an API client from an OpenAPI or gRPC service. This allows you to generate the client from a local file or URL, manage service references, and regenerate the client code if the service changes.<\/p>\n To add a new reference to an OpenAPI or gRPC service, right-click on the Connected Services node in the Solution pad and select Open Service Gallery.<\/p>\n Once you\u2019ve opened the Connected Services Gallery, you have the option to add either an OpenAPI or gRPC reference.<\/p>\n Clicking on either of the options will launch a prompt allowing you to enter the service reference, either by file path or URL.<\/p>\n You can also select whether to generate the following client class types when generating a gRPC client:<\/p>\n When generating an OpenAPI client, you can specify the namespace and additional options<\/a> which are passed through to the code generator. Code generation is based on the dotnet-grpc<\/a> and dotnet-openapi<\/a> command-line tools.<\/p>\n After generating a service reference, you can view and modify it in the Connected Services Gallery as shown below.<\/p>\n For more information on using a generated OpenAPI client, see the Getting Started with NSwag<\/a> tutorial.<\/p>\n For more information on using a generated gRPC client, see the Create a gRPC client and server in ASP.NET Core<\/a> tutorial.<\/p>\n When editing a C# class that contains unit tests, a developer can run tests using the \u201cRun Test(s)\u201d item in a context menu by right clicking in the file, the body of a test class, or the body of a test method. The context menu for the editor has been updated to include Run\/Debug Test options:<\/p>\n These new commands can be run using the following keyboard shortcuts (in the Visual Studio for Mac key bindings):<\/p>\n The Run command will run tests based on the rules below, in the \u201cRules for determining which tests to run\u201d section. Running a test is the same as selecting it in the Unit Test pad and running that test.<\/p>\n The Debug command will run tests the same as described above but will also attach the debugger when running the tests. You can customize these key bindings in the Visual Studio for Mac preferences (Visual Studio<\/strong> > Preferences<\/strong> > Environment<\/strong> > Key Bindings<\/strong>) as explained in the documentation<\/a>.<\/p>\n The Run\/Debug Test(s) commands will run one or more tests, based on the following rules.<\/p>\n As an example, using the code below\u2026<\/p>\n Here’s what happens when you right-click in different places:<\/p>\n From the solution pad, a .cs file can be right-clicked and Run\/Debug Tests commands used to run or debug all the tests in the file.<\/p>\n When customizing the keyboard shortcuts for the new test commands, the description field reads as follows:<\/p>\ngRPC and OpenAPI Client Generation<\/h2>\n
![\"Visual](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2020\/08\/word-image.png\")
<\/p>\n![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2020\/08\/word-image-1.png\")
<\/p>\n\n
![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2020\/08\/word-image-2.png\")
<\/p>\nRight-Click to Run Unit Tests<\/h2>\n
![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2020\/08\/a-screenshot-of-a-cell-phone-description-automati.png\")
<\/p>\n\n
Rules for determining which tests to run<\/h2>\n
\n
using Microsoft.VisualStudio.TestTools.UnitTesting;\r\n\r\nnamespace GardenTracker.Test\r\n{\r\n [TestClass]\r\n public class UnitTest1\r\n {\r\n [TestMethod]\r\n public void TestMethod1()\r\n {\r\n }\r\n\r\n [TestMethod]\r\n public void TestMethod2()\r\n {\r\n Assert.IsTrue(true);\r\n }\r\n }\r\n\r\n [TestClass]\r\n public class UnitTest2\r\n {\r\n [TestMethod]\r\n public void TestMethod3()\r\n {\r\n Assert.IsTrue(true);\r\n }\r\n }\r\n}<\/pre>\n\n
TestMethod1()<\/code>), just that test is executed.<\/li>\nUnitTest1<\/code> class), all tests in that class are executed.<\/li>\nRight-click in the solution pad to run tests<\/h2>\n
![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2020\/08\/a-screenshot-of-a-cell-phone-description-automati-1.png\")
<\/p>\nConfiguring Keybindings<\/h2>\n
![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2020\/08\/a-screenshot-of-a-cell-phone-description-automati-2.png\")
<\/p>\n
![\"Visual](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2020\/08\/Screen-Shot-2020-08-05-at-11.46.13-AM.png\")
<\/p>\n![\"Screenshot](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2020\/08\/a-screenshot-of-a-cell-phone-description-automati-3.png\")
<\/p>\n