anchor.diff:  <%= vars.product_windows_full %> 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 pushed app contains one or more `project.json` files.
   - The app is pushed from the output directory of the `dotnet publish` command.
   
   For information about deploying different types of .NET apps, follow the links in the table below.
  
positive.code:     </pre>
      If your <%= vars.product_windows %> 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:
  
      <pre class="terminal">
      $ cf push MY-APP -b https://github.com/cloudfoundry/dotnet-core-buildpack.git
      </pre>
  
  1. Find the URL of your app in the output from the push command and navigate to it to see your HWC app running.  In the example above, `my-app.example.com` is the URL of your app.
  
  For a basic example app, see [ASP.NET Core getting started application](https://github.com/IBM-Bluemix/aspnet-core-helloworld) in GitHub.
  
  ## <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:
  
  ```
  dotnet-core:
    sdk: 2.1.201
  ```
  
  The following formats are also valid:
  
  ```
  dotnet-core:
    sdk: 2.1.x
  
negative.code: 
  ## <a id='pushing-apps'></a> Push an App ##
  
  Follow the steps below to push your app.
  
  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:
  
  