title: Configuration management in .net
body: <p>i guess this is a hard one (for me): we have requirements for a .net (web)project which should be used with differnent configurations for different customers.</p>
  
  <p>Example: Cusomer A wants a compiled Version which includes a big part of the MainApplication but with some code excluded and two separate assemblies. Customer B wants the whole MainApplication with other assemblies and for example a different gui.</p>
  
  <p>I did a smal research and concluded with the following settings:</p>
  
  <ul>
  <li>Using the configuration manager of VisualStudio for leading to different "builds", then</li>
  <li>building the project (including several configurations) and deploying it by using NAnt</li>
  <li>Excluding code or using different code with complie directives</li>
  </ul>
  
  <p>We never did this before so i have some questions:</p>
  
  <ol>
  <li>is it possible to solve this with compile directives? (i can imagine that this point can grow very high complexity)</li>
  <li>are there better ways to fit this project (with .net)</li>
  </ol>
  
  <p>Thanks </p>