We've been using Entity framework in a production environment for many months now, and just yesterday started to get errors on some machines when querying the database using our subclass of DbContext:
"The connection string 'MyConnectionString' in the application's configuration file does not contain the required providerName attribute"
Our problem is easily solved: I adding the "providerName="System.Data.SqlClient" to the connection string in the config files on all deployed servers and workstations.
However, the mystery remains: according to the documentation:
The providerName attribute is optional, and the default is "System.Data.SqlClient".
Even more mysterious is why this started happening suddenly, and apparently only on some machines. I am not aware of any recent changes in EF or .NET versions, any SQL Server version or provider changes, or anything. But I realize there has to be something I've overlooked.
.NET 4.5 EF 5.0
Anyone have any hints or insights?
Certain driver combinations will cause the machine to be in a state where it is ambiguous which driver it should use, so it requires an explicit provider name.
It was probably some other separate application or driver install, or automatic Windows Update that ran.
Being explicit with the provider name doesn't hurt anything though. You should be fine adding it; it's only a few extra characters in your connection string. It won't ever need to change in the future or anything.
Your updated declaration should read:
<connectionStrings>
<add
name="MyConnectionStringName"
connectionString="Connection string goes here"
providerName="System.Data.SqlClient" />
</connectionStrings>
You can use too:
providerName="System.Data.EntityClient"
then:
<add name="name_here" connectionString="Data Source="pathofdatabase" providerName="System.Data.EntityClient" />
来源：https://stackoverflow.com/questions/18619848/entity-framework-providername-in-connection-string-required-all-of-the-sudde