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. <%= vars.recommended_by %> recommends using this workflow if you deploy an app in an offline setting. 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.
  +For a framework-dependent deployment (FDD), you deploy only your app and third-party dependencies. <%= vars.company_name %> recommends using this workflow if you deploy an app in an offline setting. 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:
   
  
positive.code: 
  ## <a id='offline'></a> Push an App in a Disconnected Environment
  
  For offline environments, <%= vars.recommended_by %> recommends using the Framework-Dependent Deployment workflow. This workflow enables the deployed app to use the latest runtime provided by the offline buildpack.  For more information, see: [Framework-Dependent Deployments](#framework-dependent).
  
  
  ## <a id='runtime-store'></a>Maintain ASP.NET Core Assemblies
  
  <p class="note"><strong>Note:</strong> This section applies only to source-based and framework-dependent deployments.</p>
  
  For maintaining ASP.NET Core assemblies, <%= vars.recommended_by %> recommends one of these methods:
  
  * Configure your app as a fully vendored app requiring fewer buildpack updates. Modify your `.csproj` file with the following:
  
  
negative.code:   </tr>
  </table>
  
  
  ## <a id='pushing-apps'></a> Push a .NET Core App
  
  To push a .NET Core app to a Linux Diego Cell:
  
  1. Run:
  
  