PrivacyPolicyUpdated (Enable use of unmapped properties with private setters on unmapped base classes)

The scenario here is an entity like so:

public class MyBase
{
    public int Id { get; private set; }
}

public class MyEntity : MyBase
{
}

Code First would not allow this to be mapped and furthermore if it could be mapped then core EF would not be able to write to the property. The reason for this is that PropertyInfo.CanWrite returns false if the PropertyInfo is obtained from the derived class. In addition, methods that use the setter also don't work--for example SetValue, and GetSetMethod.

The fix is to look for the PropertyInfo for the same property on the property's DeclaringType amd see whether it is writable. If it is, then this is used throughout the stack for writing.

I attempted to functional test all the areas that I could think of where EF writes to properties and I think I have caught them all.
LoadedWithHits (Make IsLoaded settable)

This change makes IsLoaded settable. It does not change any of the semantics around the flag, including cases where the flag is reset such as on FK change or entity detachment.
Code cleanup
Fixing build break caused by Code Cleanup being run on the Release configuration rather than the Debug configuration.
AssociationSet.Create was missing parameter null checks
Making DbRawSqlQuery.ToList non-generic
Renamed DbSetExtensions to IDbSetExtensions
Removing some FxCop suppressions

Work item: 998
Fixing TranslatorVisitor.Visit(MultipleDiscriminatorPolymorphicColumnMap, TranslatorArg) to pass the correct number of arguments.
Removing some unneded generics

Work item: 991
Re-enabling MARS by default
Work item: 1002
Updating XML documentation for SqlConnectionFactory
ShareAndEnjoy (Code First: Allow subclasses to map property to same database column with TPH)

EDM allows properties in different subclasses of a TPH hierarchy to map to the same database column and thereby "share" that column. Code First was building this mapping mostly correctly except that it was not fixing up the mappings to all point to the same column. This change fixes that.

Note that since the column can now be configured from multiple properties all configurations of the column must match or an exception is thrown. Configuration can be applied from any one property or from multiple properties so long as the configuration does not conflict.
adding tests for stored procdures with multiple results
addressing CR feedback
DoAsTheDocOrders (xml docs for Multiple Contexts per Database & Configurable Migrations History Table)
Also implement feedback from API review
Disabling SimpleScenariosForLocalDb tests since they seem to fail regularly on CI machine and local builds. See http://entityframework.codeplex.com/workitem/1013
MigrationsAreEmigrating (Allow migrations and context to live in different projects)

This change adds a new option of ContextProjectName for Enable-Migrations that, when specified, makes Migrations look in the given project for the DbContext for which Migrations should be enabled. Note that both the migrations project and the context project must have the Entity-Framework package installed, and ultimately the migrations project must have a reference to the context project, although this is not needed to actually run the Enable-Migrations command.
Updated xml documentation for lightweight property configurations to reflect current behavior.
corrected test name for private setters
Adding overloads for ExecuteSqlCommand and ExecuteStoreCommand that allow to deactivate automatic transaction creation.
Work item: 978
Making TransactionBehavior.Default the same as TransactionBehavior.EnsureTransaction
Runtime support for building storage association set/type mappings in the designer