{"id":71395,"date":"2017-06-20T16:30:21","date_gmt":"2017-06-20T16:30:21","guid":{"rendered":"https:\/\/www.simple-talk.com\/?p=71395"},"modified":"2021-06-03T16:47:01","modified_gmt":"2021-06-03T16:47:01","slug":"visual-studio-2017-swagger-building-documenting-web-apis","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/development\/dotnet-development\/visual-studio-2017-swagger-building-documenting-web-apis\/","title":{"rendered":"Visual Studio 2017 and Swagger: Building and Documenting Web APIs"},"content":{"rendered":"

Swagger<\/strong> is a technology-agnostic standard that allows the discovery of REST APIs, providing a way for any software to identify the features of a REST API.<\/p>\n

This is more important than it seems: It\u2019s a game changing technology, in the same way that WSDL (Web Service Description Language)<\/strong> has been for web services.<\/p>\n

WSDL<\/strong> has been the fundamental technology that made it possible for tools and IDEs such as Visual Studio<\/strong> to understand web services and to create proxy classes. This feature turns the consumption of web services into a high-level task, encapsulating all protocol details.<\/p>\n

That’s the importance of Swagger<\/strong>: It\u2019s able to do for REST APIs what WSDL has already done for web services, by allowing the creation of proxies and by making the use of web APIs much easier.<\/p>\n

VS 2017<\/strong> includes support for REST API proxy creation using Swagger protocol. It’s still in an early stage and lacking some features, however this is a great step towards the broader adoption of Swagger.<\/p>\n

We\u2019ll create an example of how we can use Swagger with VS 2017<\/strong> in order to analyze the advantages and the missing features.<\/p>\n

As well as VS 2017, we will also need IIS (Internet Information Server) installed in the development machine for our example.<\/p>\n

Development Environment<\/h2>\n

You can enable IIS as a Windows feature or server role depending if you are using a client operating system or a server one.<\/p>\n

Starting Application<\/h2>\n

Before we can use Swagger, we need a demo solution with a web API project. Let’s build this starting solution before we go on to implement Swagger.<\/p>\n

    \n
  1. Create an ASP.NET Web API project\n
      \n
    1. Inside Visual Studio, select \u2018File\u2019<\/em> -> \u2018New Project\u2019<\/em> menu<\/li>\n
    2. In the \u2018New Project\u2019<\/em> dialog box, inside the left side tree view, select \u2018Installed\u2019<\/em> -> \u2018Templates\u2019<\/em> -> \u2018Visual C#\u2019<\/em> -> \u2018Web\u2019<\/em> tree items.<\/li>\n
    3. In the \u2018New Project\u2019<\/em> dialog box, in the right side, select \u2018ASP.NET Web Application (.NET Framework)\u2019<\/em><\/li>\n
    4. In the \u2018Name\u2019<\/em> textbox, type \u2018webDemo\u2019<\/em>\n

      <\/p>\n<\/li>\n

    5. In the \u2018Solution Name\u2019<\/em> textbox, type \u2018slDemo\u2019<\/em> and click the \u2018Ok\u2019 button<\/li>\n
    6. In the \u2018New ASP.NET Web Application\u2019<\/em> window, below \u2018ASP.NET 4.5.2 Templates\u2019<\/em>, select \u2018Web API\u2019<\/em> and click the \u2018Ok\u2019 button\n

      <\/p>\n<\/li>\n<\/ol>\n<\/li>\n

    7. Configure the Web API project to use the local IIS<\/strong>\n
        \n
      1. In the \u2018Solution Explorer\u2019<\/em> window, right-click on \u2018webDemo\u2019<\/em> project and click the \u2018Properties\u2019<\/em> menu item.<\/li>\n
      2. In the right side of \u2018webDemo\u2019<\/em> properties window, click \u2018Web\u2019<\/em> page<\/li>\n
      3. In the combobox below \u2018Servers\u2019<\/em>, select \u2018Local IIS\u2019<\/em>\n

        <\/p>\n<\/li>\n

      4. Click the \u2018Create Virtual Directory\u2019<\/em> button<\/li>\n
      5. Close the \u2018webDemo\u2019<\/em> properties page<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

        This project already has a sample web API controller developed, but we need to make some changes. Let’s examine the details of the existing controller and make those changes.<\/p>\n

          \n
        1. Analyzing and changing the existing API Controller\n
            \n
          1. In the \u2018Solution Explorer\u2019<\/em> window, inside \u2018webDemo\u2019<\/em> project, open the \u2018Controllers\u2019<\/em> folder and check the existing controllers.\n

            <\/p>\n<\/li>\n

          2. Double-click the \u2018ValuesController.cs\u2019<\/em> file and check the existing actions. This is the only web API controller in the project.<\/li>\n
          3. Change the \u2018ValuesController\u2019<\/em> class for the code below. We are completing the PUT<\/strong> action and storing the list inside Application memory area.\n
                public class ValuesController : ApiController\r\n      {\r\n          private string[] lista\r\n          {\r\n              get\r\n              {\r\n                  if (System.Web.HttpContext.Current.Application[\"lista\"<\/em>]==null)\r\n                  {\r\n                      System.Web.HttpContext.Current.Application[\"lista\"<\/em>] = \r\n                          new string[] { \"value1\"<\/em>, \"value2\"<\/em> };\r\n                  }\r\n                  return \r\n                      (string[])System.Web.HttpContext.Current.Application[\"lista\"<\/em>];\r\n              }\r\n          }\r\n          public IEnumerable<string> Get()\r\n          {\r\n              return lista;\r\n          }\r\n          public string Get(int id)\r\n          {\r\n              return lista[id];\r\n          }\r\n          public void Post([FromBody]string value)\r\n          {\r\n          }\r\n          public void Put(int id, [FromBody]string value)\r\n          {\r\n              lista[id] = value;\r\n          }\r\n          public void Delete(int id)\r\n          {\r\n          }\r\n      }<\/pre>\n<\/li>\n<\/ol>\n<\/li>\n
          4. Execute the application and analyze the result<\/li>\n
          5. \n
              \n
            1. Click \u2018Start\u2019<\/em> button in the toolbar to execute the application<\/li>\n
            2. On the web page just opened, click \u2018API\u2019<\/em> link in the top menu. You will notice the API operations, basically a CRUD with two GET’s<\/strong>, one POST<\/strong>, PUT<\/strong> and DELETE<\/strong>\n
              <\/p>\n<\/li>\n
            3. In the browser navigation bar, type a new URL: http:\/\/localhost\/webDemo\/API\/Values<\/em> . As a result, a JSON<\/strong> file will be downloaded, therefore the web API is working fine.\n
              <\/p>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
              Including Swagger in our project<\/h2>\n
              Swagger<\/strong> is a technology agnostic protocol. For each technology, we need some tool to implement the protocol. SwashBuckle<\/strong> is the name of the tool for .NET. There is a version for .NET before 4.5 and another version for .NET after 4.5.<\/p>\n
              Let’s do a step-by-step walkthrough to implement Swagger using SwashBuckle<\/strong>:<\/p>\n
                \n
              1. Include SwashBuckle<\/strong> nugget package in the web API project\n
                  \n
                1. In the \u2018Solution Explorer\u2019<\/em> window, right-click the \u2018webDemo\u2019<\/em> project and click \u2018Manage nuget packet\u2019<\/em> menu item.<\/li>\n
                2. In the \u2018Nuget Package Manager\u2019<\/em> window, select \u2018Browse\u2019<\/em><\/li>\n
                3. In the textbox inside \u2018Nuget Package Manager\u2019<\/em> window, type \u2018SwashBuckle\u2019<\/em>.<\/li>\n
                4. In the left side of \u2018Nuget Package Manager\u2019<\/em> window, select \u2018SwashBuckle.Net45\u2019<\/em> package\n
                  <\/p>\n<\/li>\n
                5. In the right side of the \u2018Nuget Package Manager\u2019<\/em> window, click the \u2018Install\u2019<\/em> button.<\/li>\n
                6. In the \u2018Review Changes\u2019<\/em> window, click the \u2018Ok\u2019 button.<\/li>\n
                7. In the \u2018License Acceptance\u2019<\/em> window, click \u2018I Accept\u2019<\/em> button.<\/li>\n
                8. Close the \u2018Nuget Package Manager\u2019<\/em> window<\/li>\n<\/ol>\n<\/li>\n
                9. Configure the XML documentation. SwashBuckle<\/strong> will use the XML documentation to describe the WEB APIs actions.\n
                    \n
                  1. In the \u2018Solution Explorer\u2019<\/em> window, right-click the \u2018webDemo\u2019<\/em> project and click the \u2018Properties\u2019<\/em> menu item.<\/li>\n
                  2. In the \u2018webDemo\u2019<\/em> window, click \u2018Build\u2019<\/em> page<\/li>\n
                  3. In the \u2018webDemo\u2019<\/em> window, below \u2018Output\u2019<\/em>, click \u2018Xml Document File\u2019<\/em> checkbox. In the textbox at right you will see the path \u2018bin\\webDemo.xml\u2019<\/em>.\n
                    <\/p>\n<\/li>\n
                  4. In the \u2018Solution Explorer\u2019<\/em> window, inside \u2018webDemo\u2019<\/em> project, open the \u2018Controllers\u2019<\/em> folder and double click \u2018ValuesController.cs\u2019<\/em> file.<\/li>\n
                  5. Let’s create an XML documentation for each action and the controller. Over each action and also over the controller declaration, type \u2018\/\/\/\u2019<\/em> and describe the action and the controller.\n
                            \/\/\/ <summary>\r\n          \/\/\/ Retrieves the list of values\r\n          \/\/\/ <\/summary>\r\n          \/\/\/ <returns><\/returns>\r\n          public IEnumerable<string> Get()\r\n          {\r\n              return lista;\r\n          }\r\n          \/\/\/ <summary>\r\n          \/\/\/ Retrieves one value from the list of values\r\n          \/\/\/ <\/summary>\r\n          \/\/\/ <param name=\"id\"<\/em>>The id of the item to be retrieved<\/param>\r\n          \/\/\/ <returns><\/returns>\r\n          public string Get(int id)\r\n          {\r\n              return lista[id];\r\n          }\r\n          \/\/\/ <summary>\r\n          \/\/\/ Insert a new value in the list\r\n          \/\/\/ <\/summary>\r\n          \/\/\/ <param name=\"value\"<\/em>>New value to be inserted<\/param>\r\n          public void Post([FromBody]string value)\r\n          {\r\n          }\r\n          \/\/\/ <summary>\r\n          \/\/\/ Change a single value in the list\r\n          \/\/\/ <\/summary>\r\n          \/\/\/ <param name=\"id\"<\/em>>The id of the value to be changed<\/param>\r\n          \/\/\/ <param name=\"value\"<\/em>>The new value<\/param>\r\n          public void Put(int id, [FromBody]string value)\r\n          {\r\n              lista[id] = value;\r\n          }\r\n          \/\/\/ <summary>\r\n          \/\/\/ Delete an item from the list\r\n          \/\/\/ <\/summary>\r\n          \/\/\/ <param name=\"id\"<\/em>>id of the item to be deleted<\/param>\r\n          public void Delete(int id)\r\n          {\r\n          }<\/pre>\n<\/li>\n<\/ol>\n<\/li>\n
                  6. Configure SwashBuckle<\/strong>. For now, the only configuration we need to do is the path of the XML documentation.\n
                      \n
                    1. In the \u2018Solution Explorer\u2019 <\/em>window, inside \u2018webDemo\u2019<\/em> project, open the \u2018App_Start\u2019<\/em> folder and double click \u2018SwaggerConfig.cs\u2019<\/em> file. This file was included in the project by the \u2018SwashBuckle.Net45\u2019 <\/em>nuget package.\n
                      <\/p>\n
                      The \u2018Register\u2019<\/em> method of the \u2018SwaggerConfig\u2019<\/em> class is configured to be executed as a \u2018PreApplicationStartMethod\u2019<\/em>.<\/p>\n<\/li>\n
                    2. Include the following method inside \u2018SwaggerConfig\u2019<\/em> class:\n
                              protected static string GetXmlCommentsPath()\r\n          {\r\n              return System.String.Format(@\"{0}\\bin\\webDemo.XML\", \r\n                  System.AppDomain.CurrentDomain.BaseDirectory);\r\n          }<\/pre>\n<\/li>\n
                    3. Uncomment the following block of code inside the “Register”<\/em> method:\n
                                              c.IncludeXmlComments(GetXmlCommentsPath());<\/pre>\n<\/li>\n<\/ol>\n<\/li>\n
                    4. Execute and test the application\n
                        \n
                      1. Execute the application, click the \u2018Start\u2019<\/em> button in the toolbar.<\/li>\n
                      2. Type the following URL in the browser address bar: http:\/\/localhost\/webDemo\/Swagger\/ui\/index<\/em><\/li>\n
                      3. On the Swagger documentation page, click \u2018Values\u2019,<\/em> the name of the controller.\n
                        <\/p>\n<\/li>\n
                      4. Click each operation to see the documentation. You may notice that Swagger is using the XML documentation description for each operation.<\/li>\n
                      5. Type the following URL in the browser address bar: http:\/\/localhost\/webDemo\/Swagger\/docs\/v1<\/em> . This time we are looking for the JSON<\/strong> document describing the web API, the core result of SwashBuckle<\/strong><\/li>\n
                      6. In the question that will appear, click the \u2018Save\u2019<\/em> button (I\u2019m using Chrome, this can be a bit different with other browsers)<\/li>\n
                      7. In the message that will appear, click \u2018Open Folder\u2019<\/em> button. (I\u2019m using Chrome, this can be a bit different with other browsers)<\/li>\n
                      8. Open the v1.json<\/strong> file with Notepad. The file won’t be well formatted, the content, however, is a description of the web API, such as you can see in the image below. If you would like so, you can open the file in Visual Studio to see a well-formatted version of the file.\n
                        <\/p>\n<\/li>\n
                      9. Stop the execution in Visual Studio<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
                        Creating the Client Project<\/h2>\n
                        Now it’s time to create a client to consume our web API and illustrate how this consumption will be a lot easier.<\/p>\n
                          \n
                        1. Add a new Windows Desktop project to the solution\n
                            \n
                          1. In Visual Studio, click \u2018File\u2019<\/em> -> \u2018Add\u2019<\/em> -> \u2018New Project\u2019<\/em> in the menu<\/li>\n
                          2. In the \u2018New Project\u2019<\/em> dialog box, inside the left side tree view, select \u2018Installed\u2019<\/em>-> \u2018Templates\u2019<\/em> -> \u2018Visual C#\u2019<\/em> -> \u2018Windows Classic Desktop\u2019<\/em> tree items.<\/li>\n
                          3. In the \u2018New Project\u2019<\/em> dialog box, in the right side, select \u2018Windows Forms App (.NET Framework)\u2019<\/em><\/li>\n
                          4. In the \u2018Name\u2019<\/em> textbox, type \u2018winClient\u2019<\/em> and click the \u2018Ok\u2019 button<\/li>\n<\/ol>\n<\/li>\n
                          5. Add a reference to the web API and create the proxy\n
                              \n
                            1. In the \u2018Solution Explorer\u2019<\/em> window, right-click the \u2018winClient\u2019<\/em> project, click \u2018Add\u2019<\/em> -> \u2018REST API Client\u2019<\/em> menu item.\n
                              <\/p>\n<\/li>\n
                            2. In the \u2018Add REST API Client\u2019<\/em> window, \u2018Swagger Url\u2019<\/em> textbox, type http:\/\/localhost\/webDemo\/Swagger\/docs\/v1<\/em> .<\/li>\n
                            3. In the \u2018Client Namespace\u2019<\/em> textbox, type \u2018SvcRest\u2019<\/em> and click the \u2018Ok\u2019 button.\n
                              <\/p>\n
                              It seems that nothing happened. Inside \u2018Web Publish Activity\u2019<\/em> window you will be able to see what happened and an error message: \u2018Found operation object with duplicate OperationId ‘Values_Get’. OperationId must be unique among all operations described in the API\u2019<\/em>.<\/p>\n
                              The client tool doesn\u2019t support a REST API with operation overload, and our demo API has two GET methods. We need to resolve this problem before we proceed.<\/p>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
                              Support for operation overload<\/h2>\n
                              This lack of support for operation overload is a big flaw, since even the demo web API application, as you may be noticing, uses operation overloads, it has two GET<\/strong> actions, with and without a parameter.<\/p>\n
                              There are two possible solutions:<\/p>\n
                                \n
                              • Change the actions name to avoid an overload<\/li>\n
                              • Implement an operation filter that will intercept the JSON file creation and avoid the overload inside the JSON file.<\/li>\n<\/ul>\n
                                Let’s implement an operation filter in a step-by-step walkthrough:<\/p>\n
                                  \n
                                1. Add a new Class Library to the solution\n
                                    \n
                                  1. In the \u2018Solution Explorer\u2019<\/em> window, right-click the solution, click \u2018Add\u2019<\/em>->\u2018New Project\u2019<\/em> context menu item<\/li>\n
                                  2. In the \u2018New Project\u2019<\/em> dialog box, inside the left side tree view, select \u2018Installed\u2019<\/em>->\u2018Templates\u2019<\/em>->\u2018Visual C#\u2019<\/em> ->\u2018Windows Classic Desktop\u2019<\/em> tree items.<\/li>\n
                                  3. In the \u2018New Project\u2019<\/em> dialog box, in the right side, select \u2018Class Library (.NET Framework)\u2019<\/em><\/li>\n
                                  4. In the \u2018Name\u2019<\/em> textbox, type \u2018libTools\u2019<\/em> and click the \u2018Ok\u2019 button\n
                                    <\/p>\n<\/li>\n
                                  5. In the \u2018Solution Explorer\u2019<\/em> window, right-click \u2018Class1.cs\u2019<\/em> file, below \u2018libTools\u2019<\/em> project, and click \u2018Delete\u2019<\/em> menu item.<\/li>\n<\/ol>\n<\/li>\n
                                  6. Install the package \u2018SwashBuckle.Core.Net45\u2019 <\/em>in the new Class Library project. I\u2019m installing only the core of SwashBuckle<\/strong>, not all the libraries.\n
                                      \n
                                    1. In the \u2018Solution Explorer\u2019<\/em> window, right-click the \u2018libTools\u2019<\/em> project and click \u2018Manage nuget packet\u2019<\/em> menu item.<\/li>\n
                                    2. In the \u2018Nuget Package Manager\u2019<\/em> window, select \u2018Browse\u2019<\/em><\/li>\n
                                    3. In the textbox inside \u2018Nuget Package Manager\u2019<\/em> window, type \u2018SwashBuckle\u2019<\/em>.<\/li>\n
                                    4. In the left side of \u2018Nuget Package Manager\u2019<\/em> window, select \u2018SwashBuckle.Core.Net45\u2019<\/em> package<\/li>\n
                                    5. In the right side of \u2018Nuget Package Manager\u2019<\/em> window, click \u2018Install\u2019<\/em> button.<\/li>\n
                                    6. In the \u2018Review Changes\u2019<\/em> window, click the \u2018Ok\u2019 button.<\/li>\n
                                    7. In the \u2018License Acceptance\u2019<\/em> window, click \u2018I Accept\u2019<\/em> button.<\/li>\n<\/ol>\n<\/li>\n
                                    8. Implement the operation filter\n
                                        \n
                                      1. In the \u2018Solution Explorer\u2019<\/em> window, right-click \u2018libTools\u2019<\/em> project, click \u2018Add\u2019<\/em>-> \u2018Class…\u2019<\/em> context menu item<\/li>\n
                                      2. In the \u2018Add New Item\u2019<\/em> window, type \u2018MultipleOperationsWithSameVerbFilter.cs\u2019<\/em> in the \u2018Name\u2019<\/em> textbox.\n
                                        <\/p>\n<\/li>\n
                                      3. Copy the code below and paste inside the new file, replacing the empty class:\n
                                            using Swashbuckle.Swagger;\r\n      using System.Web.Http.Description;\r\n      public class MultipleOperationsWithSameVerbFilter : IOperationFilter\r\n      {\r\n          public void Apply(\r\n              Operation operation,\r\n              SchemaRegistry schemaRegistry,\r\n              ApiDescription apiDescription)\r\n          {\r\n              if (operation.parameters != null)\r\n              {\r\n                  operation.operationId += \"By\";\r\n                  foreach (var parm in operation.parameters)\r\n                  {\r\n                      operation.operationId += string.Format(\"{0}\",\r\n                          parm.name);\r\n                  }\r\n              }\r\n          }<\/pre>\n<\/li>\n<\/ol>\n<\/li>\n
                                      4. In the \u2018webDemo\u2019<\/em> project, add a reference to the \u2018libTools\u2019<\/em> project\n
                                          \n
                                        1. In \u2018Solution Explorer\u2019<\/em> window, right-click \u2018webDemo\u2019<\/em> project, click \u2018Add\u2019<\/em>-> \u2018Reference\u2019<\/em> context menu item<\/li>\n
                                        2. Inside \u2018Reference Manager\u2019<\/em> window, on the left side, select \u2018Projects\u2019<\/em> -> \u2018Solution\u2019<\/em> item<\/li>\n
                                        3. Inside \u2018Reference Manager\u2019<\/em> window, on the right side, check the box besides \u2018libTools\u2019<\/em> and click the \u2018Ok\u2019 button\n
                                          <\/p>\n<\/li>\n<\/ol>\n<\/li>\n
                                        4. Change Swagger <\/strong>configuration to use the new operation filter\n
                                            \n
                                          1. In the \u2018Solution Explorer\u2019<\/em> window, inside \u2018webDemo\u2019<\/em> project, open the \u2018App_Start\u2019<\/em> folder and double click \u2018SwaggerConfig.cs\u2019<\/em> file.<\/li>\n
                                          2. At the top of \u2018SwaggerConfig.cs\u2019<\/em> file, add the following line:\n
                                            using libTools;<\/pre>\n<\/li>\n
                                          3. Inside the \u2018Register\u2019<\/em> method, inside the following block:\n
                                                        GlobalConfiguration.Configuration \r\n                  .EnableSwagger(c =>\r\n                      {<\/pre>\n
                                            Add the following line of code:<\/p>\n
                                                                    c.OperationFilter<MultipleOperationsWithSameVerbFilter>();<\/pre>\n<\/li>\n<\/ol>\n<\/li>\n
                                          4. In the \u2018Solution Explorer\u2019<\/em> window, right-click the solution and click \u2018Rebuild Solution\u2019<\/em> menu item\n
                                            <\/p>\n<\/li>\n
                                          5. Repeat the step 2 of the client proxy creation, this time it will work.<\/li>\n<\/ol>\n
                                            Using the proxy in the Client Application<\/h2>\n
                                            Now the web API proxy is built inside the client project, it\u2019s time to use it to access the web API. However, the proxy needs an additional class to control authentication. Another flaw in this feature is the fact it doesn’t deal well with anonymous authentication, but we can overcome this problem with a quick fix.<\/p>\n
                                              \n
                                            1. Install the \u2018Microsoft.Rest.ClientRuntime\u2019<\/em> package in the \u2018libTools\u2019<\/em> project. This package is needed for our fix.\n
                                                \n
                                              1. In the \u2018Solution Explorer\u2019<\/em> window, right-click the \u2018libTools\u2019<\/em> project and click \u2018Manage nuget packet\u2019<\/em> menu item.<\/li>\n
                                              2. In the \u2018Nuget Package Manager\u2019<\/em> window, select \u2018Browse\u2019<\/em><\/li>\n
                                              3. In the textbox inside \u2018Nuget Package Manager\u2019<\/em> window, type \u2018Microsoft.Rest.ClientRuntime\u2019<\/em>.<\/li>\n
                                              4. In the left side of \u2018Nuget Package Manager\u2019<\/em> window, select \u2018Microsoft.Rest.ClientRuntime\u2019<\/em> package<\/li>\n
                                              5. In the right side of \u2018Nuget Package Manager\u2019<\/em> window, click \u2018Install\u2019<\/em> button.<\/li>\n
                                              6. In the \u2018Review Changes\u2019<\/em> window, click the \u2018Ok\u2019 button.<\/li>\n
                                              7. In the \u2018License Acceptance\u2019<\/em> window, click \u2018I Accept\u2019<\/em> button.<\/li>\n<\/ol>\n<\/li>\n
                                              8. Implement the AnonymousCredential<\/strong> class. It will sove the anonymous authentication problem.\n
                                                  \n
                                                1. In the \u2018Solution Explorer\u2019<\/em> window, right-click \u2018libTools\u2019<\/em> project and click \u2018Add\u2019<\/em>-> \u2018Class\u2019<\/em> context menu item.<\/li>\n
                                                2. In the \u2018Add new item\u2019<\/em> dialog box, type \u2018AnonymousCredential.cs\u2019<\/em> in \u2018Name\u2019<\/em> textbox and click the \u2018Ok\u2019 button<\/li>\n
                                                3. In the top of the new file, add the following statement:\n
                                                  using Microsoft.Rest;<\/pre>\n<\/li>\n
                                                4. Use the following code for this class. Yes, nothing is needed but the inheritance.\n
                                                  public class AnonymousCredential : ServiceClientCredentials\r\n  {\r\n  }<\/pre>\n<\/li>\n<\/ol>\n<\/li>\n
                                                5. 3) Build the client Windows form to access the API\n
                                                    \n
                                                  1. In the \u2018Solution Explorer\u2019<\/em> window, below \u2018winClient\u2019<\/em> project, double-click \u2018Form1.cs\u2019<\/em> file.<\/li>\n
                                                  2. From the \u2018Toolbox\u2019<\/em> window, add three buttons inside the form.<\/li>\n
                                                  3. Change the button properties according to the following:\n
                                                    Name: cmdAllValues 
                                                    \n Text: All Values<\/p>\n
                                                    Name: cmdValue 
                                                    \n Text: Single Value<\/p>\n
                                                    Name: cmdUpdate 
                                                    \n Text: Update<\/p>\n
                                                    <\/p>\n<\/li>\n<\/ol>\n<\/li>\n
                                                  4. In the Windows project, add a reference to the \u2018libTools\u2019<\/em> project\n
                                                      \n
                                                    1. In the \u2018Solution Explorer\u2019<\/em> window, right-click \u2018winClient\u2019<\/em> project, click \u2018Add\u2019<\/em>-> \u2018Reference\u2019<\/em> context menu item<\/li>\n
                                                    2. Inside \u2018Reference Manager\u2019<\/em> window, on the left side, select \u2018Projects\u2019<\/em> -> \u2018Solution\u2019<\/em> item<\/li>\n
                                                    3. Inside \u2018Reference Manager\u2019<\/em> window, on the right side, check the box besides \u2018libTools\u2019<\/em> and click the \u2018Ok\u2019 button<\/li>\n<\/ol>\n<\/li>\n
                                                    4. Add the code for the \u2018All Values\u2019<\/em> button\n
                                                        \n
                                                      1. Select the \u2018Form1.cs (design)\u2019<\/em> page<\/li>\n
                                                      2. Double click the \u2018All Values\u2019<\/em> button, this will create a click event for the button.<\/li>\n
                                                      3. In the top of the \u2018Form1.cs\u2019<\/em> file (already opened by the previous task), add the following statements:\n
                                                        using libTools;\r\n  using svcRest;<\/pre>\n<\/li>\n
                                                      4. Change the \u2018cmdAllValues_Click\u2019<\/em> for the following code:\n
                                                                private async void cmdAllValues_Click(object sender, EventArgs e)\r\n          {\r\n              SvcRestClient client = \r\n                  new SvcRestClient(new Uri(\"http:\/\/localhost\/webDemo\"),\r\n                      new AnonymousCredential());\r\n              var result = client.Values.Get();\r\n          \r\n              foreach(var x in result)\r\n              {\r\n                  MessageBox.Show(x);\r\n              }\r\n          }<\/pre>\n
                                                        It’s important to notice the following details:<\/p>\n