title: MSBuild file VS SLN and Project files
body: <p>I am just starting to look at MSBuild and get my head round the whole idea.  I have setup a CI Server with Hudson and want to know how I "should" deal with build scripts and the sln / proj files.</p>
  
  <p>For example I have an existing solution that has 10 projects in it, (one being a website and another being the web deployment project, and the setup MSI project).  What is a good way of dealing with the building of this?</p>
  
  <ol>
  <li>should I just point msbuild at the sln file?</li>
  <li>Should I take what is in the SLN file and create another, so it points at the different proj files?</li>
  <li>Should I take the code from all the sln and proj files and create one custom build script?</li>
  </ol>
  
  <p>If I do either of the last two, do I have to worry about maintaining two sets of scripts, i.e. making sure my script is upto date as well as the sln / proj files?</p>
  
  <p>Also how do I deal with building it when developing on my local box?  Do I just CTRL SHIFT B to build it and then only use the build script for the CI server / deployment builds?</p>