anchor.diff:  
   
   
  -1. To externalize your `Web.config` and `Web.Release.config` files, tokenize each of the files' 
  -environment-specific properties using the format `#{configPath:key}`.  
  +1. Tokenize your `Web.Debug.config` and `Web.Release.config` environment-specific properties by replacing hard-coded values 
  +with tokens following the format `#{configPath:key}`.  
   <br>
       For example:  
   <br>
  -    **Web.Config**
  -
  -    ```xml
  -    <connectionStrings>
  -        <add name="MyDB" 
  -             connectionString="#{connectionStrings:MyDB}"  />
  -    </connectionStrings>
  -    ```
  -
  -    **Web.Release.config**
  +
  +    **Tokenized Web.Release.config**
   
       ```xml
       <?xml version="1.0" encoding="utf-8"?>
  
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: 
  ## <a id='move-to-spring-cloud'></a> Move Configuration Settings to Spring Cloud Config Server 
  
  You must store your environment-specific transformations in a secured environment for your deployment to be production-ready.  
  
  A multi-environment, production-ready deployment configuration can be achieved by using Spring Cloud Config Server 
  backed by transforms stored in a git repository data source.
  
  To modify your transformations for use by Spring Cloud Config Server, complete the following steps:   
  
  1. Determine your manifest file's `ASPNETCORE_ENVIRONMENT` environment variable value.  
  1. Create a network accessible git repository for each application.  
  1. Create a YAML file to hold your common settings across all environments.  
  <br>
      Name the file `YOUR-APPLICATION`.yaml.  
  <br>
      Where `YOUR-APPLICATION` is the identifier name for your application.  
  <br>
      For example:  
  <br> 
      **sampleapp.yaml**  
  
      ```yaml
      appSettings:
        Setting1: "Common setting1"  
        ```
  
  1. Create separate YAML files for each unique environment to hold your environment-specific settings.  
  <br>
      Name the files `YOUR-APPLICATION`-`APP-ENVIRONMENT`.yaml.  
  <br>
      Where:  
      * `YOUR-APPLICATION` is the identifier name for your application.  
      * `APP-ENVIRONMENT` is the `ASPNETCORE_ENVIRONMENT` environment variable value.  
  
      For example:  
  <br> 
      **sampleapp-Development.yaml**  
  
      ```yaml
       connectionStrings:
         MyDB: "Data Source=devserver;Initial Catalog=mydb;User ID=serviceacc3;Password=PaKsAsEwWoOrOdT3"
      ```
  
      **sampleapp-Production.yaml**  
  
      ```yaml
       connectionStrings:
         MyDB: "Data Source=prodserver;Initial Catalog=mydb;User ID=serviceacc3;Password=PaKsAsEwWoOrOdT3"
      ```    
  
  
  ## <a id='create-spring-cloud-service'></a> Create a Configuration Service for Spring Cloud Config Server
  
  