anchor.diff:      </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>
  +    <pre>cf push APP-NAME -b https://github.com/cloudfoundry/dotnet-core-buildpack.git</pre>
  +
  +    Where `APP-NAME` is the name of your app.
   
   1. Find the URL of your app in the output from the push command and navigate to it to see your app running.  In the example above, `my-app.example.com` is the URL of your app.
   
  
positive.code: 
  * Use `cf set-env` to set the `CACHE_NUGET_PACKAGES` environment variable on the command line:
  
      <pre class="terminal">$ cf set-env YOUR-APP CACHE_NUGET_PACKAGES false</pre>
  
  For more information, see the [Environment Variables](../../devguide/deploy-apps/manifest.html#env-block) section
  of the <em>Deploying with Application Manifests</em> topic.
  
negative.code: When using the SCD workflow for deploying your app,
  you must specify a runtime in the `dotnet publish` command. For example:
  
  <pre class='terminal'>
  $ dotnet publish -r ubuntu14.04-x64
  </pre>
  
  In addition, you must include the specified runtime in the `RuntimeIdentifiers` section of the project file.
  
  