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:   sdk: 2.x
  ```
  
  ```
  dotnet-core:
    sdk: 2.x.x
  ```
  
  The buildpack chooses which SDK to install based on the files present at the app root, according to the following order of precedence:
  
  1. `buildpack.yml`
  2. `global.json`
  3. If the app contains only `*.fsproj` files, the buildpack installs the latest 1.1.x SDK.
  
  <p class="note"><strong>Note</strong>: The app respects the SDK version specified in <code>global.json</code> at runtime. If you provide versions in both <code>global.json</code> and <code>buildpack.yml</code>, ensure that you specify the same versions in both files.</p>
  
  
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:
  