title: Is it possible to configure a .NET application to use a different config file without specifically adopting the source code to support such a need?
body: <p>I have a .NET application. Its source code performs no config file manipulations. I am wondering whether there is a way to instruct the CLR to bind the app to another config file. A command line switch is perfect, but as far as I know no such thing exists.</p>
  
  <p>A registry change could be a solution, as long as it is consulted only during the application start, because I wish to run two instances of the app with different config files. So, if the registry is consulted during the app lifetime - no good.</p>
  
  <p>Anyway, there could be other options. Still, I am unaware of any.</p>
  
  <p>Anyone?</p>
  
  <p>Thanks.</p>