anchor.diff:      Where:  
       * `APP-NAME` is your app's name.  
       * `VERSION` is the buildpack version.   
  -    * `SETTING-NAME` is the name of a configuration setting used by your app. Create as many NAME : "VALUE" pair lines as are needed by your app.  
  -    * `SETTING-VALUE` is the development value of the setting. Create as many NAME : "VALUE" pair lines as are needed by your app.  
  +    * `SETTING-NAME` is the name of a configuration setting used by your app. 
  +    * `SETTING-VALUE` is the development value of the setting. 
   
       For example:
   
  
positive.code: * Linux, Windows or MacOS development machine or VM.
  * A foundation with Windows cells available to push to.
  
  
  ## <a id='overview'></a> Overview
  
  To run legacy ASP.Net applications configuration settings are typically injected through Web.config files. 
  As per cloud-native principles, an app's build artifacts should not include configuration settings.  
  
  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:  
  
  
negative.code:     <connectionStrings>
          <add name="MyDB" 
               connectionString="Data Source=LocalSQLServer;Initial Catalog=MyReleaseDB;User ID=serviceacc3;Password=PaKsAsEwWoOrOdT3" />
      </connectionStrings>
      ```
  
      **Web.Debug.config**
  
      ```xml
      <connectionStrings>
          <add name="TestDB" 
               connectionString="Data Source=ReleaseSQLServer;Initial Catalog=TestDB010;User ID=testaccount;Password=ABC123!" 
               xdt:Transform="SetAttributes" 
               xdt:Locator="Match(name)"/>
      </connectionStrings>
      ```
  
  