anchor.diff:      ```
       This allows the buildpack to pass the correct port from `$PORT` to the app when running the initial startup command.
   
  -1. Remove the following line from the `Main` method.
  +1. Remove the following line from the `Main` method:
   
       ```c#
       .UseContentRoot(Directory.GetCurrentDirectory())
       ```
   
  -1. Add this line after `.UseKestrel()`:
  +1. Add the following line after `.UseKestrel()`:
   
       ```c#
       .UseConfiguration(config)
       ```
   
  -1. Either add `Microsoft.Extensions.Confugration.CommandLine` as a dependency using `project.json`:
  +1. Add `Microsoft.Extensions.Confugration.CommandLine` as a dependency using one of the following:
  +    - `project.json`:
  +        
  +		  ```json
  +        "Microsoft.Extensions.Configuration.CommandLine": "1.0.0",
  +        ```
  +    - `*.csproj`:
   
  -    ```json
  -    "Microsoft.Extensions.Configuration.CommandLine": "1.0.0",
  -    ```
  -
  -1. Or using `*.csproj`:
  -
  -    ```xml
  -    <PackageReference Include="Microsoft.Extensions.Configuration.CommandLine">
  -        <Version>1.0.0</Version>
  -    </PackageReference>
  -    ```
  +        ```xml
  +        <PackageReference Include="Microsoft.Extensions.Configuration.CommandLine">
  +            <Version>1.0.0</Version>
  +        </PackageReference>
  +        ```
   
   1. Remove the following line from the `Startup` method:
   
  
positive.code: 
  1. If your app requires any other files at runtime, such as JSON configuration files, add them to the `include` section of `copyToOutput`.
  
  1. Save.
  
  With these changes, the `dotnet run` command copies your app `Views` to the build output, where the .NET CLI can find them. Refer to the following example `Main` method:
  
  
negative.code: Specify any non-default package sources in the `NuGet.Config` file.
  
  For a basic example, see this [Hello World sample](https://github.com/IBM-Bluemix/aspnet-core-helloworld).
  
  ## <a id='cli_tools'></a> .NET Core SDKs ##
  
  The first several releases of the .NET Core SDKs used `project.json` files for project build configuration. The current release of the .NET Core SDK uses MSBuild as its build tool, which uses `*.csproj` and `*.fsproj` files for configuration.
  
  Currently, the .NET Core buildpack includes both types of SDKs. If the pushed app contains a `global.json` file, the buildpack installs the version specified by that file. Otherwise, the buildpack chooses which SDK to install as follows:
  
  1. If the app only contains `project.json` files, the buildpack installs the latest SDK that supports this configuration.
  2. If the app only contains `*.csproj` and `*.fsproj` files, the buildpack installs the latest SDK that uses MSBuild.
  3. If the app contains both file types without a `global.json`, the buildpack throws an error, as it cannot determine the proper SDK to install.
  
  <p class="note"><strong>Note</strong>: Microsoft has removed support for project.json from the <a href="https://blogs.msdn.microsoft.com/dotnet/2016/11/16/announcing-net-core-tools-msbuild-alpha/">.NET Core SDK tools</a>. Consequently, support for <code>project.json</code> apps in the buildpack will soon be deprecated.
  </p>
  
  ## <a id='port'></a>Configure the Listen Port ##
  
  For your .NET Core app to work on Cloud Foundry, you must modify the `Main` method to configure the app to listen on the port specified by the `$PORT` environment variable, which Cloud Foundry sets automatically.
  
  1. Open the file that contains your `Main` method.
  
  1. Add a `using` statement to the top of the file.
  
      ```c#
      using Microsoft.Extensions.Configuration;
  