anchor.diff:  dotnet publish -r ubuntu14.04-x64
   ```
   
  -The specified runtime should also be included in the `RuntimeIdenfiers` section of the project file.
  +The specified runtime should also be included in the `RuntimeIdentifiers` section of the project file.
   
   See [more details for FDD vs SCD deployments](https://docs.microsoft.com/en-us/dotnet/core/deploying/)
   
   
  -## <a id='offline'></a>Offline Workflow - Push an App in a Disconnected Environment##
  -
  -Using the [Framework Dependent Deployment (FDD) workflow](#framework-dependent) is the recommended deployment method for an offline environment, as it will allow the deployed application to use the latest runtime provided by the offline buildpack. It is possible to use the [Self-Contained Deployment (SCD) workflow](#self-contained) in an offline setting, but it is not recommended.
  -
  -## <a id='runtime-store'></a>Runtime Package Store
  -*This section applies only to source-based and framework-dependent deployment workflows*
  -
  -
  -The recommended workflow for maintaining AspNetCore assemblies is to update your `.csproj` file with:
  -
  -```
  -<PropertyGroup>
  -  <PublishWithAspNetCoreTargetManifest>false</PublishWithAspNetCoreTargetManifest>
  -</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='dotnet-sdk'></a> .NET Core SDKs ##
  +## <a id='dotnet-sdk'></a> Specifying .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:
   
   ```
  
positive.code: </PropertyGroup>
  ```
  
  ###.runtimeconfig.json Apps
  
  In a `.runtimeconfig.json` app, the latest .NET Framework patch version is used by default. To pin to a specific .NET Framework version, add the `applyPatches` property and set it to `false`.
  
  ```
  {
  
negative.code: 
  For a basic example app, see [ASP.NET Core getting started application](https://github.com/IBM-Bluemix/aspnet-core-helloworld) in GitHub.
  
  ## <a id='source-based'></a>Source-based, Non-published Workflow
  
  To use this workflow, simply `cf push` the source code for your app (i.e. not the resultant directory of a `dotnet publish`).
  
  This is the recommended workflow because the buildpack can keep all your dependencies in-sync and up-to-date.
  When using this workflow, here are some edge-cases you may run into:
  
  ### <a id='multiple-projects'></a>Deploy Apps with Multiple Projects
  
  To deploy an app that contains multiple projects, you must specify a main project for the buildpack to run. Create a `.deployment` file in the root folder of the app which sets the path to the main project as follows:
  
  ```text
  [config]
  project = <main project>
  ```
  
  1. Set `project` to the `*.csproj` or `*.fsproj` file of the main project.
  
  For example, if an app contains three projects in the `src` folder (the main project `MyApp.Web`, `MyApp.DAL`, and `MyApp.Services`), format the `.deployment` file as follows:
  
  ```text
  [config]
  project = src/MyApp.Web/MyApp.Web.csproj
  ```
  
  In this example, the buildpack automatically compiles the `MyApp.DAL` and `MyApp.Services` projects if the `MyApp.Web.csproj` file of the main project lists them as dependencies. The buildpack attempts to execute the main project with `dotnet run -p src/MyApp.Web/MyApp.Web.csproj`.
  
  ### <a id='non-default-package-sources'></a>Using Non-Default Package Sources
  
  To deploy an app that uses non-default package sources, you must specify those package sources in the [`NuGet.Config` file](https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file).
  For a basic example, see this [Hello World sample](https://github.com/IBM-Bluemix/aspnet-core-helloworld).
  
  ### <a id='disabling-nuget'></a>Disabling and Clearing the NuGet Package Cache
  
  You may need to disable NuGet package caching, or clear NuGet packages cached in the staging environment, in one of the following scenarios:
  