anchor.diff:  </PropertyGroup>
   ```
   
  -### <a id='dotnet-runtime-fdd'></a>For framework-dependent apps
  -
  -In your `.runtimeconfig.json` app, the latest .NET Runtime patch version is used by default. To pin to a specific .NET Runtime version, add the `applyPatches` property and set it to `false`.
  +### <a id='dotnet-runtime-fdd'></a>Framework-Dependent Apps
  +
  +In your `.runtimeconfig.json` app, the latest .NET Runtime patch version is used by default.
  +To pin to a specific .NET Runtime version, add the `applyPatches` property and set it to `false`.
   
   ```
   {
  
positive.code: </PropertyGroup>
  ```
  
  This is results in a fully vendored app but will require fewer buildpack updates.
  
  If you do not want to use this option you can set `buildpack.yml` to your desired .NET SDK line to keep the SDK up to date:
  
  ```
  
  ---
  dotnet-core:
  	sdk: 2.0.x
  ```
  
  **Note:** Dotnet releases `2.0.x` AspNetCore assemblies in the `2.1.200`-`2.1.299` SDK versions. `2.1.x` assemblies are released in the `2.1.300` and above SDK versions.
  
  ## <a id='port'></a>Configure the Listen Port ##
  
  For your .NET Core app to work on <%= vars.product_windows %>, you must modify the `Main` method to configure the app to listen on the port specified by the `$PORT` environment variable. <%= vars.product_windows %> sets this environment variable automatically.
  
  1. Open the file that contains your `Main` method.
  
  
negative.code: 
      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 in `*.csproj`:
  
      ```
      <PackageReference Include="Microsoft.Extensions.Configuration.CommandLine">
          <Version>VERSION</Version>
      </PackageReference>
      ```
  
      In the above example, replace `VERSION` with the version of the package to use. You can find valid versions at https://www.nuget.org.
  
  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 your changes.
  
  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:
  
  ```c#
  public static void Main(string[] args)
  