anchor.diff:  
       This allows the buildpack to pass the correct port from `$PORT` to the app when running the initial startup command.
   
  -
  -
  -
  -1. Add `Microsoft.Extensions.Configuration.CommandLine` as a dependency using one of the following:
  -    - `project.json`:
  -
  -		```json
  -        "Microsoft.Extensions.Configuration.CommandLine": "VERSION",
  -        ```
  +1. Add `Microsoft.Extensions.Configuration.CommandLine` as a dependency:
       - `*.csproj`:
   
           ```xml
  
positive.code: $ cf push MY-APP -b https://github.com/cloudfoundry/dotnet-core-buildpack.git
  </pre>
  
  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 ##
  
  To pin the .NET Core SDK to a specific version or version line, create a `buildpack.yml` file at the app root and add the following:
  
  ```
  
negative.code: Cloud Foundry automatically uses the .NET Core buildpack when one or more of the following conditions are met:
  
  - The pushed app contains one or more `*.csproj` or `*.fsproj` files.
  - The app is pushed from the output directory of the `dotnet publish` command.
  
  If your Cloud Foundry deployment does not have the .NET Core buildpack installed or the installed version is out of date, push your app with the `-b` option to specify the buildpack:
  