title: Tell web references to use web.config or how to make settings.settings editable
body: <p>I am migrating an ASP.NET 2.0 (3.5 SP1) app to .NET 4.0. It leverages SQL Server Reporting Services 2008R2 web service. This web service is an old-school asmx soap web service. </p>
  
  <p>Back then I added a web-reference which I set to dynamic and this opted in some configuration code in my <code>&lt;applicationSettings&gt;</code> of the <code>web.config</code>.</p>
  
  <p>After migrating to Visual Studio 2010 and .Net 4.0 I had to re-add the web reference. The .Net 2.0 web references dialog adds the proxy class as it was. But now it includes a <code>settings.settings</code> file to my project in the <code>Properties</code> folder. I could live with that but the <code>settings.settings</code> file is not available after compilation. It looks like it has been compiled into the dll.</p>
  
  <p>Even pasting the <code>settings.settings</code> config in my <code>web.config</code> and deleting the <code>settings.settings</code> file does not help. I get a namespace compilation error because the vs-generated proxy class expected the <code>settings.settings</code>...</p>
  
  <p>So how can I include my web reference and make it adjustable within a configuration file?</p>
  
  <p>Either tell the web reference editor to use <code>web.config</code>, maybe?
  Or make the <code>settings.settings</code> file available as xml so it could be changed on deployment?</p>
  
  <p>Or any other help would be fantastic too...</p>