Add Clean to the list of default targets
Bump version to 6.0.1
Remove non-public documentation comments
That's soooo 2008... (1679: Model validation is failing for a valid model after changeset 082b451c17b)

The problem was that we were not restricting property lookup to declared properties only when scanning navigation properties in attribute-based mapping. This was not caught due to lack of coverage for attribute-based mapping. This has been added using dynamic assembly creation in the functional tests so that it does not impact all the POCO mapping we have. (POCO and attribute-based mapping cannot coexist in the same assembly.)
Merge branch 'hotfix-6.0.1'

Conflicts:
	src/SharedAssemblyVersionInfo.cs
	test/EntityFramework/UnitTests/Utilities/AssemblyExtensionsTests.cs
	tools/EntityFramework.settings.targets
Bump version to 6.1.0-alpha1
Remove StyleCop suppressions
Copy of a... (First fix for 1454: Code First models still get built more than once in EF6)

The culprit here is EdmxWriter which is used to create an EDMX for use by Migrations and the differ. Previously it would always build the model again. Now if we are in the middle of doing DbContext initialization, then a model cached on the internal context is used instead. This cached model is released after initialization has finished so that we don't keep a potentially large model around forever.
Merge branch 'hotfix-6.0.1'
Issue 1322 - make maxlength configurable
Added some additional unit tests
How many diffs would a diff differ diff if a diff differ diffed differently? (Avoid calling differ after database creation)

Currently the differ is used in three ways when running through database initialization scenarios:
1. To actually do a diff of the model in __MigrationHistory to the current model
2. A diff from the empty model to the current model as a mechanism for building the list of commands to create the database if needed
3. To determine if a database is up-to-date after being created in order to decide whether or not to run the Seed method

For 3 the Seed method is never called anyway (because the MigrationsConfig is generated by us and has an empty Seed implementation) so we can avoid doing the diff.
Merge branch 'hotfix-6.0.1'
Mapping API: Entity/Association sets and container.
畢昇 (More support for using Type with newer Reflection APIs)

This change adds support for the following members of Type that are not supported in .NET for Windows Store apps:
- Assembly property -> Assembly() extension method
- BaseType property -> BaseType() extension method
- IsGenericType property -> IsGenericType() extension method
- IsGenericTypeDefinition property -> IsGenericTypeDefinition() extension method
- Attributes property -> Attributes() extension method
- IsClass property -> IsClass() extension method
- IsInterface property -> IsInterface() extension method
- IsValueType property -> IsValueType() extension method
- IsAbstract property -> IsAbstract() extension method
- IsSealed property -> IsSealed() extension method
- IsEnum property -> IsEnum() extension method
- IsSerializable property -> IsSerializable() extension method
- ContainsGenericParameters property -> ContainsGenericParameters() extension method
- IsSubclassOf method -> IsSubclassOf() extension method

Also added support for getting fields and constructors, and updated some of the property and method APIs to be clearer, use params, and use less #ifdefed code on .NET 4.
Hit me baby one less time... (Reduce number of database accesses on initialization)

Currently when running a database initializer we sometimes end up checking for database existence and querying for migrations multiple times. This originally kept a better factoring with less coupling between Migrations and the initializer code. However, it could also cause performance issues, especially when using database initializers to create databases. In the worst cases we would call Exists five times and make four queries to find the correct history table. This has been reduced to one exists check and fewer Migrations queries in three ways:
- Recording the database existence state from the initial database table checker call and passing this down through internal APIs to where it can be used by Migrations.
- Fixing a bug where InternalContext would sometimes pass in an additional null schema to Migrations.
- Changing the order the Migrations queries for history tables so that in the case where the history table exists (common default path for Code First) we now do fewer queries. The case where the history table doesn't exist potentially now does an extra query, but if the database has no metadata then initialzers can be completely disabled for perf anyway.
Small change to (hopefully) fix net40 build with older compiler.