Before we look at the options for

changing the database name, let's delete our current database.

Deleting a database is not an operation that you'll do very often,

especially given that deleting a database

means that you'll forever lose access to the data contained within it.

Since our database is being generated by our app, and

it doesn't contain any data that we need to keep, it's safe to do.

We can delete our database by right-clicking here,

on the database in the SQL Server Object Explorer, and selecting Delete.

We'll be asked if we also want to delete the backup and

restore history information, and close any existing connections.

Be sure to check both options, that'll ensure that the delete operation will

succeed, even if we currently have an open connection to the database.

We're going to look at three options for

changing the name of the generated database.

The first and easiest of these options is to add a constructor to our context class.

And call the base class constructor that accepts a parameter for

the database name or connection string.

Public Context() then colon followed by the base keyword,

which allows us to call the members in the base class.

In this case, the base class constructor.

We'll take a look at how to use the connection string option in just a moment.

For now I'll just pass in the name of the database that

I'd like to use, ComicBookGallery.

Now let's run the app Press Enter to continue execution.

Then refresh the list of databases in the SQL Server Object Explorer window,

and we'll see our new ComicBookGallery database.

The DbContext base class constructor that we're calling

also accepts the database connection string.

This is our second option for changing the name of the database.

Here in Notepad, I have an example of a SQL Server database connection string.

The Data Source value is the name of the database server that we want to connect

to, which is a localdb instance named MSSQLLocalDB.

If we wanted to use a different database server other than localdb, or

a differently named instance, we could change this value.

The Initial Catalog value is the name of the database.

The Integrated Security value indicates that we want to use

Windows authentication.

And the MultipleActiveResultSets value indicates that we want to be able to run

more than one SQL batch on an open connection at the same time.

Setting this value to true, generally speaking,

helps to improve the overall performance of retrieving data from the database.

For more information about multiple active result sets, or

MARS, see the teacher's notes.

I'll copy and paste the connection string to the base class constructor method call.

Because our connection string contains a backslash, which is used to escape special

characters and text, we need to add another backslash before our backslash.

This tells the compiler that we actually want a backslash character, or

we can leave the single backslash and add an at sign before the starting quote.

This tells the compiler to treat our text as a verbatim string literal and

ignore any escape sequences contained within the text.

Let's also add the text ConnectionString as a suffix to the initial catalog name so

we don't have to delete our existing database.

Run the app again, and press Enter to continue execution.

Refresh the list of databases, and

we'll see our new ComicBookGalleryConnectionString database.

The third and last option for

changing the name of the database is to add a database connection string whose

name matches the name of our context class to our apps configuration file.

For console apps, we'll use the App.config file

in the root our project to add the necessary configuration.

For ASP.NET MVC apps,

you can use the web.config file in the root of the project.

We'll be covering how to use Entity Framework within MVC apps in another

course.

We start by adding a connectionStrings element right underneath

the root configuration element.

And within that element, we'll add an add element.

On the add element,

we'll add a name attribute whose value will match the name of our context class.

That's how EF will know to associate this connection string with our context.

Then we'll add a connection string attribute for our connection string,

which I'll cut and paste from the context class.

I'll also change the database name suffix to AppConfig.

Lastly, we'll add a providerName attribute to indicate which data provider to use.

Since we're using a SQL Server localdb database,

I'll set the value to System.Data.SqlClient.

Now that we have our connection string defined in the App.config file,

we can remove the constructor from the context class.

Run the app again, and press Enter to continue execution.

Refresh the list of databases, and

we'll see our new ComicBookGalleryAppConfig database.

Of the three options that we just saw, I like the third option, as it keeps

the configuration of our database location and name out of our code.

That makes it possible to change the location or

name of the database without having to rewrite our code.

Which is especially helpful when deployment applications

into other environments.

Let's remove the AppConfig suffix from the database name in the connectionString, so

our database name is just ComicBookGallery.

Then I'll do some cleanup and delete all of the existing databases.

Lastly, I'll run the app one more time, and

verify that our database is successfully created.

Refresh the list of databases, And here's our ComicBookGallery database.