Keyword not supported: "data source" initializing Entity Framework Context

Question

I'm initializing Entity Framework Object context, and this gives me the keyword not supported error:

metadata=res://*/MainDB.csdl|res://*/MainDB.ssdl|res://*/MainDB.msl;provider=System.Data.SqlClient;provider connection string="Data Source=.\SQLEXPRESS;AttachDbFilename=D:\Workspace\vs\Leftouch\Leftouch.Web\Data\Leftouch.mdf;Integrated Security=True;Connect Timeout=30;User Instance=True;App=EntityFramework"

I took the connection string directly from web.config which was working, and modified only the path to the file (which I set dynamically), and instead of using the default value, used this connection string explicitly. What could cause this error?

Please refer http://stackoverflow.com/questions/6003085/how-do-i-programmatically-set-the-connection-string-for-entity-framework-code-fi for a different approach — LCJ, Jul 18 '12 at 12:31
I don't know who came up with this `metadata=res:`, then `res=somethingelse` with `"` all over the place syntax - but they should be really glad they aren't in the same room as me right now :-/ — Simon_Weaver, Apr 20 '17 at 00:16
2018 .Net EF Core similar syntax error - providerName was not needed by a SqlClient connection string. Also no quotes or ticks in string for EF core. — Sql Surfer, Jun 26 '18 at 21:39

score 340 · Accepted Answer · edited Feb 22 '20 at 16:57

340

The real reason you were getting this error is because of the " values in your connection string.

If you replace those with single quotes then it will work fine.

https://learn.microsoft.com/archive/blogs/rickandy/explicit-connection-string-for-ef

(Posted so others can get the fix faster than I did.)

edited Feb 22 '20 at 16:57

Callum Watkins

2,844
4
29
49

answered Aug 09 '11 at 23:14

Vaccano

78,325
149
468
850

1

If you are passing in the connection string to the ObjectContent class, make sure that it has single quotes. If you are getting the connection from the .config file, then it is okay to use the " escape sequence. – Mike Stonis May 10 '12 at 23:45
For those of you not familiar with how XML works, `"` is an escape sequence for a quotation mark because it is a reserved character in XML. – Vivian River Oct 09 '12 at 14:38
System.Data.EntityClient.EntityConnectionStringBuilder made it for me, thank you. – AFract Sep 15 '15 at 14:02
The blog link in your post gave me awareness about `EntityConnectionStringBuilder` class. Thank you. +1. – RBT Dec 25 '16 at 02:09

score 38 · Answer 2 · answered Jul 27 '16 at 15:21

38

I fixed this by changing EntityClient back to SqlClient, even though I was using Entity Framework.

So my complete connection string was in the format:

<add name="DefaultConnection" connectionString="Data Source=localhost;Initial Catalog=xxx;Persist Security Info=True;User ID=xxx;Password=xxx" providerName="System.Data.SqlClient" />

answered Jul 27 '16 at 15:21

Savage

2,296
2
30
40

2

Worked for me! +1 – Yury Kerbitskov Dec 02 '16 at 11:25
6

The above change will potentially lead to (as in my case) the following error "The context is being used in Code First mode with code that was generated from an EDMX file for either Database First or Model First development" – Psi-Ed Dec 19 '16 at 09:45
You can comment throw new UnintentionalCodeFirstException() in OnModelCreating(), but it looks like a dirty workaround – Alexander Ulmaskulov Sep 05 '18 at 09:36

score 14 · Answer 3 · answered Aug 09 '11 at 15:02

14

This appears to be missing the providerName="System.Data.EntityClient" bit. Sure you got the whole thing?

answered Aug 09 '11 at 15:02

Craig Stuntz

125,891
12
252
273

Ok, that was another attribute, forgot that one. Added it now it is `metadata=res://*/MainDB.csdl|res://*/MainDB.ssdl|res://*/MainDB.msl;provider=System.Data.SqlClient;provider name=System.Data.EntityClient;provider connection string="{0};App=EntityFramework"` and it now says key not found: provider name. I've also tried `providerName=...` instead of `provider name=` too, but no luck. – Can Poyrazoğlu Aug 09 '11 at 18:03
2

Well, I started to create it using the `EntityConnectionStringBuilder` class, and weirdly, it's working now. But I still have no idea why it wasn't accepting my string, even with your additions. – Can Poyrazoğlu Aug 09 '11 at 18:49

score 3 · Answer 4 · answered Apr 20 '15 at 19:57

3

Believe it or not, renaming LinqPad.exe.config to LinqPad.config solved this problem.

answered Apr 20 '15 at 19:57

Sameer Alibhai

3,092
4
36
36

13

This is Microsoft, anything can be happened ! – Altaf Patel Jul 06 '15 at 15:17
This doesn't make sense. What has Linqpad to do with the question and how can renaming an executable ever be helpful? – Gert Arnold Dec 26 '19 at 21:15
Well this particular error occured with Linqpad in my case and doing this resolved it. And I didn't rename the executable. I renamed the .exe.config to .config. – Sameer Alibhai Dec 27 '19 at 01:07
Anyway, it's a very specific scenario. It only adds noise as it doesn't *explain* anything, – Gert Arnold Dec 27 '19 at 20:56

score 2 · Answer 5 · answered Dec 26 '19 at 14:19

2

Make sure you have Data Source and not DataSource in your connection string. The space is important. Trust me. I'm an idiot.

answered Dec 26 '19 at 14:19

Hairgami_Master

5,429
10
45
66

score 1 · Answer 6 · answered Sep 26 '19 at 14:16

1

Just use \" instead ", it should resolve the issue.

answered Sep 26 '19 at 14:16

Nilesh Moradiya

31
3

Keyword not supported: "data source" initializing Entity Framework Context

6 Answers6

Linked