After reading this page, when trying to use this option to Xamarin portable app client (from a swagger json file), I get the following message:

Generating client code and adding to project started
Generate client code for REST API with following parameters:
REST API Name: MyProject API info, Base namespace: MyProject.App, Metadata file path: C:\Users\weitz\OneDrive\Documents\Visual Studio 2015\Projects\MyProject\src\MyProject\swagger.json
Exception: Could not load file or assembly 'Newtonsoft.Json, Version=7.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.
Generating client code and adding to project failed
Adding REST API client for failed

Steps to reproduce:

• Create VS 2015 ASP.NET Core API app and add swagger with its UI and configure it
• Run the app and save the swagger.json file (link appears on the header)
• Add a portable Xamarin or Prism project
• Add Newtonsoft.Json package via nuget
• Right click the client project -> Add -> REST API client
• Choose Select an existing Swagger metadata file and browse to the saved file
• The following error shows up (text copied above):
  

Hello,

Thank you for the tutorial. As I was going through the tutorial I was naming my resources differently because I plan to build on top of this. I'm probably not the only one doing that. For the most part, there was enough coverage in the tutorial for me to do this without breaking anything. However, there was just one point where I broke it and that was by renaming the url key (#3 under "Configure the middle tier to call the data tier").

The behaviour I was getting was that I was getting 500 response codes after trying to call the api.

The fix was that I updated the string on line 42 to the correct key.

Cheers!
Ethan

I've been attempting to implement CORS configuration via arm templates.

I have used this template as a guide, specifically this section.

{
          "apiVersion": "2015-04-01",
          "name": "web",
          "type": "config",
          "dependsOn": [
            "[resourceId('Microsoft.Web/Sites', variables('apiSiteName'))]"
          ],
          "properties": {
            "cors": {
              "allowedOrigins": [
                "[concat('https://', parameters('siteName'), '.azurewebsites.net')]"
              ]
            }
          }
},

I've attached this resource within the resources array of an existing Microsoft.Web/Sites object.

The template deploys successfully. No errors are returned.

The CORS configuration is not updated however, the entry does not appear in the Azure Portal either?

Is this really a valid way of setting CORS configurations?

https://schema.management.azure.com/schemas/2016-08-01/Microsoft.Web.json#/resourceDefinitions/sites_config suggests it is correct.