CodePlex 1698: The input contains property mappings for an entity type in C space, but only those matching the table name of the current EntityMappingConfiguration are supposed to be configured at that stage (for entity splitting scenarios). The problem was that a table name may not be set or it may be set on the parent EntityTypeConfiguration for all its mapping configurations, in which cases TableName was null, and TableName.Equals threw NullReferrenceException.
CodePlex 1614: Added default instance and using it throughout the code.
Added comment that explains why TableName comparison is necessary.
HoneyIShrunkThePackage
Removing EntityFramework.PowerShell.dll from the EntityFramework.SqlServerCompact Nuget package
It's abstract, but it's not art... (1289 & 1747: Mapping bug when abstract type is not explicitly added to the model)

Code First starts off by building EntityTypeMappings for a default TPH model. These mappings are not always valid because of at least two things: abstract types are excluded by default and some types in the TPH hierarchy must be changed to IsTypeOf mappings. Abstract types are excluded by default because they sometimes will not appear in the mappings. However, quite often they will appear, so we later attempt to add back abstract types if they are discovered in some other way--such as being configured explicitly. This means that later still when the entity mappings are fixed up for IsTypeOf changes and to remove unused fragments the code must take into account abstract types. So not mapping them by default was not much help and made it harder to find issues because, as in these bugs, the mappings for the abstract types were not added by any other path and so never got added.

The fix is to include abstract types by default and then let the later code remove them if not necessary when doing the mapping fix-up. This change revealed a couple of bugs in the fix-up code where abstract types were not being considered; these have been fixed. Also, we were using the lack of a type mapping as an indication of an abstract type with no mapped derived types in order to throw an early exception for this invalid mapping. That check is now moved to the point where we process all the entity types in the model.
DisorderlyConduct - fixing bug https://entityframework.codeplex.com/workitem/1735: Designer: Can not reverse engineer EDMX when FKs in different order than PKs (composite keys)

When validating the model we assumed that the order of primary key columns of the principal entity is the same as the order of the foreign key columns of the dependent entity. This is true for models built using Code First but does not have to be true for database first models where the order of columns is already defined in the database. Fixing validation to look the PK properties up by name based on the values specified in ReferentialConstraint for the prinicpal entity.
Using public types in SqlCe provider
fixing ps scripts paths for azure and provider agnostic runs. CR: LukeW