Identity theft for dummies...

Allow SQL Server-specific value generation strategies to be used.

This change adds fluent API for setting Identity or Sequence value generation for integer properties when using SQL Server. Note that Migrations support is still missing--this change only includes a hack to stop Identity columns being generated when sequences are being used.

Currently the default is still Identity. It will be switched to Sequence once Migrations support is added.
fix to issue 691 - we were incorrectly constructing foreign keys by convention in case of composite keys. CR: Arthur
Enabling Built-In Data Types tests for Azure Table Storage. Added a
non-null property to all Built-In data types classes to support having a
PartitionKey and RowId for Azure Table Storage.
Making WithCurrentCulture have the same signature on all platforms allowing it to unify.
U Can't Touch This...

Stop generating values for properties for which a value has been set.

We currently check against the default value for the property type; I will file an issue for allowing this check to be specified, which would then also allow it to be disregarded entirely such that this behavior is switched off.
Fixed the redis case
Add a direct reference to regular expressions.
Added System.Text.RegularExpressions
Added Regex again...
Positive Tests for Negative Cases (adding tests for database error page)
Adding a few end-to-end tests for database error page
Also enabling shared API tests