Read Before Building Cicero.txt

Visual Studio 2010 has a serious bug which Microsoft refuses to fix:

https://connect.microsoft.com/VisualStudio/feedback/details/556158/batch-build-links-to-wrong-referenced-projects

In essence, building Cicero by using Build -> Batch Build can produce bizarre
and unpredictable broken builds, depending on which Solution configuration is
selected when performing the build (this is the drop-down selection next to
Visual Studio's "run" button).

Recommended steps to workaround this bug when building Cicero for distribution:

 -- Optional Pre-Build-Cleanup --
1) Close Visual Studio (to release its lock on certain files which will be
cleaned)

2) Ensure that you do not have any important files within the Cicero directory
structure that are not being track by the git repository (they will get deleted
with the following command!).

3) At the git command prompt, from the top level of the Cicero git repository,
run "git clean -f -x -d"

-- Building --

4) Start Visual Studio again, and load the solution. 
Select "Release" as the current configuration and select Build -> Build Solution
5) Select "Atticus-Release-x86" and then Build -> Build Solution
6) Select "Atticus-Release-x64" and then Build -> Build Solution



Release build outputs are copied by post-build scripts to the ReleaseBuilds
directory in the main solution directory. This ReleaseBuilds directory can
then be zipped up for distribution.