anchor.diff:      </connectionStrings>
       ```
   
  -    <p class='note'><strong>Note:</strong> Web and WCF apps are created with <strong>Debug</strong> and <strong>Release</strong> configurations 
  -    of the <code>Web.Debug.config</code>, and <code>Web.Release.config</code> web config transformation files. 
  -    When debugging on a developer machine, transform the <code>Debug</code> <code>Web.Debug.config</code> file and use the <code>Debug</code> configuration profile.
  -    </p> 
  +
   
   1. To externalize your `Web.config` and `Web.Release.config` files, tokenize each of the files' 
   environment-specific properties using the format `#{configPath:key}`.  
  
positive.code: ---
  title: Creating an Extension Buildpack for ASP.NET Apps
  owner: Buildpacks
  ---
  
  This topic explains how to write a Web Config Transform Extension Buildpack for ASP.NET apps.  
  
  ## <a id='prerequisites'></a>Prerequisites
  
  * Linux or MacOS development machine or VM
  * [golang](https://golang.org/) v1.10 or later programming language
  * [direnv](https://direnv.net/) environment variable manager for your shell
  
  
  ## <a id='overview'></a> Overview
  
negative.code: The Web Config Transform Extension Buildpack injects environment-specific appSettings and connectionString values 
  into legacy ASP.Net app containers by performing token replacements during `cf push` staging.
  
  To leverage the Web Config Transform Extension Buildpack, complete the following procedures:  
  
  1. [Identify Environment Dependent Configurations and Externalize](#tokenize)
  1. [Create a Parameterized Cloud Foundry App Manifest](#create-manifest)
  