anchor.diff:  
   1. Push your app.
   
  -**Note**: Do not set `applyPatches: false` in  `*.runtimeconfig.json`. This will prevent your app from receiving updates to the runtime version and assemblies.
  +**Note**: Unless you want to pin your .NET Framework to a specific version (see below), do not set `applyPatches: false` in  `*.runtimeconfig.json`, as this will prevent your app from receiving updates to the runtime version and assemblies.
  +
   
   ## <a id='self-contained'></a>Self-Contained Deployments (SCD) Workflow ##
   This workflow is not recommended. Because this workflow results in a prepublished binary, we are unable to keep all your dependencies in-sync and up-to-date.
  
positive.code: 
  <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> files, ensure that you specify the same versions in both files.</p>
  
  ## <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.
  
  1. Add a `using` statement to the top of the file.
  
      ```c#
      using Microsoft.Extensions.Configuration;
      ```
  
  1. Add the following lines before the line `var host = new WebHostBuilder()`:
  
      ```c#
      var config = new ConfigurationBuilder()
          .AddCommandLine(args)
          .Build();
      ```
  1. Add the following line after `.UseKestrel()`:
  
      ```c#
      .UseConfiguration(config)
      ```
  
      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`:
  
  		```
          "Microsoft.Extensions.Configuration.CommandLine": "VERSION",
          ```
      - `*.csproj`:
  
          ```xml
          <PackageReference Include="Microsoft.Extensions.Configuration.CommandLine">
              <Version>VERSION</Version>
          </PackageReference>
          ```
  
      In the above examples, replace `VERSION` with the version of the package to use. Valid versions can be found 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)
  {
      var config = new ConfigurationBuilder()
          .AddCommandLine(args)
          .Build();
  
      var host = new WebHostBuilder()
          .UseKestrel()
          .UseConfiguration(config)
          .UseContentRoot(Directory.GetCurrentDirectory())
          .UseStartup<Startup>()
          .Build();
      host.Run();
  }
  ```
  
  ## <a id='specify-version'></a>Specify a .NET Framework Version
  
  Specify a minor version of the .NET Framework.
  Do not specify a patch version, because
  buildpacks contain only the two most recent patch versions of each minor version.
  
  ###.csproj Apps
  Add the following to a `.csproj` app to lock the .NET Framework version:
  
  ```
  <PropertyGroup>
  
negative.code: ## <a id='pushing-apps'></a> Push an App ##
  
  Follow the steps below to push your application.
  
  1. Run `cf push APP-NAME` command to push your app, where `APP-NAME` is the name you want to give your app. For example:
  
  