Preview of useful design-time features for DbContext.
When right-clicking on a C# project, the following context menu function is supported:
1) Reverse Engineer Code First - Generates POCO classes, derived DbContext and Code First mapping for an existing database.
I received error when do"reverse engineer code first" command ."System.Data.ProviderIncompatibleException: The provider did not return a ProviderManifestToken string. ---> System.InvalidOperationException: This operation requires a connection to the 'master' database. Unable to create a connection to the 'master' database because the original database connection has been opened and credentials have been removed from the connection string. Supply an unopened connection. ---> System.Data.SqlClient.SqlException: Login failed for user 'sa'."
Typical of EF team: fill vital need with "CTP" tool, promptly break with next revision, let tool languish in obsolescence. Now you get to choose having really useful tools or using the latest version of EF. But who needs this tool really? All your users should have dbo privileges on your database and perform their own migration, right?
EF Power Tools is a good and useful tool, but there is a problem with usage of existing DbContext with connection string from the *.config file. Code-First fluent mapping can also be generated from database for Oracle, MySQL, PostgreSQL, and SQLite by Devart Entity Developer: http://www.devart.com/blogs/dotconnect/index.php/using-entity-framework-power-tools-ctp1-with-oracle-mysql-postgresql-and-sqlite.html .