ASP.NET Entity Framework code-first connection string for SQL Server mdf file, where is it and how do I change it?

Question

I am launching my asp.net application and am having issues with some databases that were created locally. I need to change their connection string for the program to point to my new online SQL Server database but I can't find any way to do that. I created these databases locally using the Entity Framework code-first scaffolding. This is my code for the db context:

public class SubjectDbContext : DbContext
{
    public DbSet<Subject> SubjectDatabase { get; set; }
}

And I made it into a .mdf using this method:

Which automatically generates the database using constructors (according to https://msdn.microsoft.com/en-us/library/jj653752(v=vs.110).aspx#localdbtosse). That's what I was able to figure out.

I really need to find these connection strings so I can change them because otherwise I don't know how to get my published application online to access its respective databases.

Remaking these databases is not really an option. So I need to find AND change the connection strings for them. Now the connection strings are not in the web.config file. In fact deleting all the connection strings in the web.config file does not stop these databases from working locally. So they must be stored somewhere else.

How can I change these connection strings. If I can't my application won't work online.

The closest post I could find to this question was: Code first: Where's the connection string & the Database?

but it doesn't answer the question. Thanks for any help or links.

If you search your entire solution for the MDF filename do you find anything? Its annoying when you search, get a hit but then find the question isn't answered hey! — Nick.Mc
– Nick.Mc, Commented Apr 13, 2017 at 0:55
Maybe that question is saying that if you add that entry it will automatically be used? — Nick.Mc
– Nick.Mc, Commented Apr 13, 2017 at 0:56
searching the whole solution only yeilds the file in the app data folder. I mean this must be an issue people commonly run into because how else would you be able to use these custom db contexts in a deployed web app, if you scaffolded them with default settings?. either that or ive done something really wrong, or something is really wrong in my app. — Tyler S. Loeper
– Tyler S. Loeper, Commented Apr 13, 2017 at 2:31
and I tried adding an entry with the connection name switched to the dbcontext name, but sadly it didnt work either. I'm starting to feel like remaking these databases might be the only way to get these connection string to change — Tyler S. Loeper
– Tyler S. Loeper, Commented Apr 13, 2017 at 2:43

marc_s · Accepted Answer · 2017-04-13 04:53:34Z

1

The default Connection string gets added in Web.config by the name "DefaultConnection".

And the database files gets created under App_Data folder of your application.(Click 'Show All files' to see the databases file or browse to the App_Data folder path in explorer).

This is how you do migrations after having the DefaultConnection set to your new server:

Change SubjectDbContext to as below, adding constructor:

public class SubjectDbContext : System.Data.Entity.DbContext
{
    public SubjectDbContext() : base("DefaultConnection")
    {
    }

    public DbSet<Subject> SubjectDatabase { get; set; }
}

Run command in Package Manager Console:
```
Enable-Migrations -ContextTypeName SubjectDbContext -MigrationsDirectory Migrations\SubjectDbContext
```
It will create Configuration.cs in Migrations/SubjectDbContext folder
Set AutomaticMigrationsEnabled = true; in Configuration constructor. Can add seed code if required.

Run the below command in Package Manager Console, to create the database and its tables:

Update-Database -ConfigurationTypeName [Replacewith namespace].SubjectDbContext.Configuration –Verbose

edited Apr 13, 2017 at 4:53

marc_s

760k186 gold badges1.4k silver badges1.5k bronze badges

answered Apr 13, 2017 at 2:05

Boney

2,2223 gold badges21 silver badges25 bronze badges

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

8 Comments

Tyler S. Loeper Over a year ago

Nope. Ive been using the webconfig file in the root folder. It has a default connection string. But changing this connection string to my server has not resulted in these other databases working online in the published app, and in fact deleting the default connection string does not stop the local db (apart from login) from working locally either for these other db.

Tyler S. Loeper Over a year ago

I'll post my connection string, maybe that will help

Tyler S. Loeper Over a year ago

It used to be: <add name="DefaultConnection" connectionString="Data Source=(LocalDb)\MSSQLLocalDB;AttachDbFilename="|DataDirectory|\aspnet-BA Portal-20170128030249.mdf";Initial Catalog="aspnet-BA Portal-20170128030249";Integrated Security=True" providerName="System.Data.SqlClient" />

Tyler S. Loeper Over a year ago

and now its: <add name="DefaultConnection" connectionString="Data Source=184.163.194.53;Integrated Security=False;database=my_banaturalportal;User ID=my_banaturalportal_user;Password=Temp**!;Connect Timeout=1500;" providerName="System.Data.SqlClient" />

Boney Over a year ago

I have edited the answer on how to create DBs/Tables in the server.

|

Collectives™ on Stack Overflow

ASP.NET Entity Framework code-first connection string for SQL Server mdf file, where is it and how do I change it?

1 Answer 1

8 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

8 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related