Code-first always working with SQL Server Express or SQL Server CE

Question

I'm building a MVC 3 application and use Entity Framework 4.3 code-first. My context is becoming complex so I've decided to working with SQL Server 2008 R2. Then I changed my connection string in web.config. I checked and I know the new connection string is correct, but EF is still working with the default connection string (.\SQLEXPRESS ...) from SQL Server CE (I have now deleted SQL Server CE from nuget packages).

My context name is CodeFirstContext and my connection string name is CodeFirstContext, too. But the return context.Products; always fails and/because the connection string in context says SQLEXPRESS (my web.config sets the connection string to SQLSERVER).

What is going on here? I erased all default connection strings in the project. When I am running the project, it still gets all data from SQL Server Express.

I have been searching for about two days. Why is this so difficult if so many people only have to change the connection string and then it works.

Jaimal Chohan · Accepted Answer · 2012-05-04 14:03:34Z

1

You might be picking up the connection string from your root/machine config, in your web.config file add a clear element like so

<connectionStrings>
  <clear/>
  .. your connection strings here
...

edited May 4, 2012 at 14:03

answered May 4, 2012 at 13:20

Jaimal Chohan

8,6557 gold badges45 silver badges65 bronze badges

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

1 Comment

Eray Aydogdu Over a year ago

same connectionstring is working fine on another test application(it's not code-first)

Eray Aydogdu · Accepted Answer · 2012-05-05 09:38:13Z

1

I 've solved the problem like that:

public class CodeFirstContext : DbContext
{
    public CodeFirstContext() : base("RandevuIzle")
    {
    }
    public DbSet<User> Users { get; set; }
}


<connectionStrings>
  <add name="RandevuIzle" connectionString="Data Source=111.222.333.444\MSSQLSERVER2008; Initial Catalog=RandevuIzle;User Id=MyUserName;Password=myPassword" providerName="System.Data.SqlClient" />

Somethings went wrong but i cannot understand. I re-start the project after doing this code below. Then it's work normally.

answered May 5, 2012 at 9:38

Eray Aydogdu

2501 gold badge4 silver badges17 bronze badges

Comments

robrich · Accepted Answer · 2012-05-04 14:27:27Z

0

As you instantiate your DbContext, are you providing a name that isn't CodeFirstContext?

answered May 4, 2012 at 14:27

robrich

13.3k7 gold badges39 silver badges63 bronze badges

Comments

beauXjames · Accepted Answer · 2013-02-24 22:04:20Z

Holy SQL Smoke, Batman! This drove me totally batty today. Getting EF 5.0 up and running w/ VS2010 on a new project was much more difficult than I imagined. I had the same problem and found this great Ode to the Code ::

http://odetocode.com/blogs/scott/archive/2012/08/15/a-troubleshooting-guide-for-entity-framework-connections-amp-migrations.aspx

And to be specific ::

 public class DepartmentDb : DbContext 
 {
    public DepartmentDb()
        : base(@"data source=.; 
                 initial catalog=departments;
                 integrated security=true")
    { }

    public DbSet<Person> People { get; set; }
}

Got me the result I was needing. Do I think it's cool that I've got to set the data source like this and that it won't find the obvious solution within the app.config? No, I don't. But I have officially spent too much time attempting a transition from LINQ to SQL over to EF today and am going to go ahead and get some of the application done while I still have some interest in doing so.

Collectives™ on Stack Overflow

Code-first always working with SQL Server Express or SQL Server CE

4 Answers 4

1 Comment

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

1 Comment

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related