title: WebReference creates App.config even in library assembly project
body: <p>Why does adding a web reference to a library assembly project create an app.config file for the project?  it will not be used at run time, right ?  - as there can only be one root config file per host process (executable), - That's why only executables get their app.configs renamed to "projectName.exe.config" and deployed to output folder during compile process.  </p>
  
  <p>In any event, the only thing that's in there is a applicationSettings section with one configuration setting with the url to the web service, which generally is going to be dynamically set by ops using a separate configuration setting anyway...</p>
  
  <p>Also, if a host process has several dependant library assemblies with web references, what's the point?  Which of the many settings (one per each dependant library assembly) would get used? </p>
  
  <p>Anyway, I want to get rid of these app.configs, to avoid the exception when the configuration system cannot find the setting at runtime, but as I'm not clear on why it's there in the first place... Am I missing something ?</p>