anchor.diff:  
   ## <a id='framework-dependent'></a>Framework-Dependent Deployments##
   
  -For a framework-dependent deployment (FDD), you deploy only your app and third-party dependencies.
  -Cloud Foundry recommends using this workflow if you deploy an app in an offline setting.
  +This is the recommended workflow if you deploy an app in an offline setting.
  +
  +In a framework-dependent deployment (FDD), you deploy only your app and third-party dependencies.
   For information about deploying FDDs, see
   [Framework-dependent deployments (FDD)](https://docs.microsoft.com/en-us/dotnet/core/deploying/index#framework-dependent-deployments-fdd)
   in the Microsoft documentation.
  -
   To deploy an FDD using the buildpack, do the following:
   
   1. Publish the app by running the `dotnet publish [-f YOUR-FRAMEWORK] [-c Release]` command.
   
  -1. Navigate to the `bin/Release/YOUR-FRAMEWORK/YOUR-RUNTIME/publish` directory.
  +1. Navigate to the `bin/Debug|Release/YOUR-FRAMEWORK/YOUR-RUNTIME>/publish` directory.
   Alternatively, if your app uses a `manifest.yml`, specify a path to the output folder of `dotnet publish`.
   This allows you to push your app from any directory.
   
  
positive.code: For information about `NuGet.Config`,
  see [nuget.config reference](https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file)
  in the Microsoft documentation.
  
  ### <a id='disabling-nuget'></a>Disable and Clear Your 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:
  
  * Your app fails to stage because it runs out of space, exceeding the maximum allowable disk quota.
  * You have added pre-release packages to test a new feature and then decided to revert back to the main NuGet feed.
  You may need to remove the packages you changed from the cache to avoid conflicts.
  
  Disabling NuGet caching clears any existing NuGet dependencies from the staging cache
  and prevents the buildpack from adding NuGet dependencies to the staging cache.
  
  To disable NuGet package caching, set the `CACHE_NUGET_PACKAGES` environment variable to `false`.
  If the variable is not set, no change is required.
  
  To set `CACHE_NUGET_PACKAGES` to `false`, do one of the following:
  
  * Locate your app manifest, `manifest.yml`, and set the `CACHE_NUGET_PACKAGES` environment variable to `false`:
  
      ```
      ---
      applications:
      - name: sample-aspnetcore-app
  
negative.code: 
  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>Use Non-Default Package Sources
  
  