DbContextExtensions fail in case of multiple containers in the workspace
Less misleading function signatures in DbContextExtensions taking parameter "Type entityType" instead of "string entityTypeName"
Find a proper EdmEntityType by the corresponding CLR type even if there are two containers with entities whos types have the same Name but different Namespaces
Created test: Apply_Changes_Should_Mark_Multiple_OrderDetails_Added
Created Test: Existing_Parent_With_Added_Children_Should_Have_Children_Marked_As_Added
Renamed acceptance test features. Created test: AddOrderDetails.
Fixed error in DbContextExtensions.ApplyChanges adding multiple child entities. Updated unit and acceptance tests.
Extend the Clone_Of_ChangeTrackingCollection_Should_Create_Deep_Copy unit test to demonstrate that the IEnumerable.Clone extension method doesn't preserve object references correctly
Fix: IEnumerable.Clone/ChangeTrackingCollection.GetChanges don't preserve object references correctly
DONT PUSH: my local connection string
Merge remote-tracking branch 'remotes/az-codepex/DbContextExtensions.OSpace' into MY-develop