I ran into a similar problem .. and there is a very funny solution for this. Just peek into your ConnectionString. If this is the same that you used for other ASP.Net applications, then this should not be. Entity Framework has a completely different case
<add name="EmployeeContext" connectionString="Server=.\SQLEXPRESS;Database=DB1;User Id=user1;password=password1;" providerName="System.Data.SqlClient**;**" />
Change it to -
<add name="EmployeeContext" connectionString="Server=.\SQLEXPRESS;Database=DB1;User Id=user1;password=password1;" providerName="System.Data.SqlClient"/>
Can you tell the difference ... only one small one - No! '; at the end of ProviderName .. Yes, and that matters. It should be the same with the same ProviderName copy, although I did not check case sensitivity. But that solved my problem.
Ambuj source share