title: Visual Studio "Add Service Reference" keeps adding "extendedProtectionPolicy" to my config file
body: <p>When I add a Service Reference in Visual Studio to a service, it keeps adding this <code>extendedProtectionPolicy</code> to my Security Bindings, which on my Win7 machine it works fine. But when I deploy to Server 2003 it errors out saying unrecognized element in configuration file.</p>
  
  <p>Removing the line <code>&lt;extendedProtectionPolicy policyEnforcement="Never" /&gt;</code> fixes the error.</p>
  
  <p>This is the entire portion of unwanted web.config generated after an Add Service Reference (client side)</p>
  
  <pre><code>&lt;security mode="TransportWithMessageCredential"&gt;
      &lt;transport clientCredentialType="None" proxyCredentialType="None"
          realm=""&gt;
          &lt;extendedProtectionPolicy policyEnforcement="Never" /&gt;
      &lt;/transport&gt;
      &lt;message clientCredentialType="UserName" algorithmSuite="Default" /&gt;
  &lt;/security&gt;
  </code></pre>
  
  <p>Here is the behavior my service is using (iis7-host side)</p>
  
  <pre><code>&lt;behavior name="GetHttpsIncludeFaults"&gt;
    &lt;serviceCredentials&gt;
      &lt;userNameAuthentication 
        userNamePasswordValidationMode="Custom" 
        customUserNamePasswordValidatorType="MyCustomValidator, MyOtherAssembly"/&gt;
    &lt;/serviceCredentials&gt;
    &lt;serviceMetadata httpsGetEnabled="true" /&gt;
    &lt;serviceDebug includeExceptionDetailInFaults="true" /&gt;
  &lt;/behavior&gt;
  </code></pre>
  
  <p>I'd like to point out a few things. This happens in both VS2010 and VS2008. This happens in Consumer Projects of ASP.NET-MVC flavor AS WELL AS Windows Service / WPF Application.</p>