-Started refactoring MSBuild task into its own separate project.

-The updater now lists the database version before it begins applying updates.  This actually resolves an issue that occurrs if you are running SchemaManager for the first time with the RebuildCurrentVersion flag set.
-Removed custom version of SpecsFor, added real version.

-Removed references to test code from the Utilities project.
Now supports change scripts that have 'go' statements that aren't all upper case.
Increased batch command timeout to 5 minutes.
-Schema changes now have up to 30 minutes to execute.  This isn't ideal, but it's necessary for long-running migrations.

-Fixed a bug that was causing multi-line comments to be split incorrectly.
-Added better error logging.

-Added a 30 minute timeout to the transaction.
Converted from 3-digit version numbers to 4 digit.  The first 3 digits follow SemVar versioning while the last is a script number to track which scripts have been executed against the database.
Added support for "Run Always" scripts.  Fixed a few bugs left over from the switch to SemVar-style versioning.
Fixed a couple of bugs.

Added support for a "WhatIf" flag.
Added better database setup scripts.
Schema Manager now either commits or rolls back all changes as a single transaction.  This makes it easier to ensure that your database always remains in a consistent state.
Schema Manager now runs all update (or rollback) scripts as a single atomic transaction.  This means your database will always be in a consistent state.  Also added a "hack" to override the maximum transaction timeout for TransactionScope.
CommandWrapper now assumes ownership of the underlying SqlConnection if you pass it a closed connection.
Schema Manager now uses a single connection for all updates.  This makes it compatible with SQL Server 2k5 without escalating to the MSDTC.
Changed how DbContext behaves, it now works with SQL Server 2005 *and* will fully roll back all scripts in the event of an error.
Upgraded solution to VS 2012.
Timeout can now be specified for the batch transaction.
Changes can now be committed incrementally instead of as one big batch.  This is useful for updates that take a long time or apply a lot of updates.
Also fixed a few bugs around not disposing of resources correctly as part of this.