Entity Framework code first tries to open wrong database

Question

I am writing an ASP MVC 3 application. I am using Sql Server 2008 R2 for my database.

I created my data model and my DbContext called EFDbContext. I created my database which is named SportsStore.

My connection string is:

<add name="EFDbContext" connectionString="Data Source=.\SQLEXPRESS;Initial Catalog=SportsStore;Integrated Security=True;Pooling=False" providerName="System.Data.SqlClient" />

I run the app and no data is shown.

I figured out that EF automatically generates a new database SportsStore.Domain.Concrete.EFDbContext, but I want it to use SportsStore which I have previously created, and to automatically map my model properties to table columns. If I disable the autogenerate database feature I get the following error:

Cannot open database "SportsStore.Domain.Concrete.EFDbContext" requested by the login

Shouldn't Entity Framework try to open SportsStore database? Why is it trying to open that one? Do I have a mistaken connection string?

What is constructor of your EFDbContext class looks like? Did you pass the connection string to it? You could pass a connection string to the DBContext constructor or set the connection string in the web.config file with the name of your context class. blogs.msdn.com/b/adonet/archive/2011/01/27/… — Felix
– Felix, Commented Jan 26, 2012 at 23:15

danludwig · Accepted Answer · 2012-01-27 08:12:00Z

2

Strange... have you tried this for your connection string? I think you need MARS to do some things with DbContext.

<add name="EFDbContext" connectionString="Data Source=LOCALHOST\SQLEXPRESS;Initial Catalog=SportsStore;Integrated Security=True;MultipleActiveResultSets=True;" providerName="System.Data.SqlClient" />

Those are the only things different than one of my projects where this works. You are sure the class & connection string are named exactly alike? Did you try naming the connection string like this?

<add name="SportsStore.Domain.Concrete.EFDbContext" connectionString="Data Source=.\SQLEXPRESS;Initial Catalog=SportsStore;Integrated Security=True;Pooling=False" providerName="System.Data.SqlClient" />

answered Jan 27, 2012 at 8:12

danludwig

47.3k27 gold badges164 silver badges240 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Gonzalo Over a year ago

Ok I'll try that when i get home. I forgot to say that my model is in a different project, so its in a separate dll. I think that entity framework, which is working from domain.dll, is not even reading the web.config file in my mvc app. Maybe I need to create an app.config for domain.dll and set my connection string over there.

Oybek · Accepted Answer · 2012-01-27 08:44:03Z

2

I can give you just a suggestion. I came accross with a similar difficulties when I have my DbContext and corresponding connectionstring in one project (usually class library). However it ignores the latter if you use it in other project like win forms. It tries to get the connection string from the startup project's config file.

If this is your case try to place your connection string in your startup project config file.

answered Jan 27, 2012 at 8:44

Oybek

7,2945 gold badges32 silver badges50 bronze badges

2 Comments

Gonzalo Over a year ago

I have an mvc app, which is my startup project, and domain.dll where I have my model. The connection string is in web.config in the mvc app. I think that it's not being read, so EF creates a new database named the same as my context. I'll try to set my connection string in app.config for domain.dll and see what happens.

aBetterGamer Over a year ago

I ran into this same issue. The configuration needs to be in the startup project.

nilesh · Accepted Answer · 2012-03-17 09:43:11Z

1

hmm.I was getting same error.after some effort i realized that i had put connection string in wrong Web.config file.There are two web config files.One under view folder and another under the project.You need to add connection string in one under the project folder

answered Mar 17, 2012 at 9:43

nilesh

261 bronze badge

Comments

Xavi López · Accepted Answer · 2013-05-23 10:43:47Z

1

I had commented out the default connection string and placed mine underneath:

<connectionStrings>
<!--<add name="DefaultConnection" connectionString="Data Source=(LocalDb)\v11.0;Initial Catalog=aspnet-MvcMovie-20130509163734;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnet-Mvc4Movie-20130509163734.mdf" providerName="System.Data.SqlClient" />-->
<add name="MoveieDBContext" ...

This made EF ignore my connection string and generate its own. Uncommenting the default connection made EF use mine and it all worked.

edited May 23, 2013 at 10:43

Xavi López

27.9k11 gold badges100 silver badges167 bronze badges

answered May 23, 2013 at 10:25

Jon

111 bronze badge

Collectives™ on Stack Overflow

Entity Framework code first tries to open wrong database

4 Answers 4

1 Comment

2 Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

1 Comment

2 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related