Entity Framework dose not create database in the localdb - asp.net

Question

I am new to MVC, and right now I am trying to work out the example demonstrated in professional Asp.Net MVC 4 by Galloway J and others, in this example I have to do the following :
create 3 classes: Album, Genre, Artist
create DBContext class called MusicStoreDB
create a controller call it store manager.
in the scaffolding options I used MVC controller with read/ write actions and views, using Entity framework
I also set an Initializer to recreate the database always on application start
but when running the solution no database created, what could be the problem I have tried lot of suggestions, even reinstalling the sql server 2008 R2 and, VS 2012 but it dose not work.
this is the global.asax file
Imports System.Web.Optimization
Imports System.Data.Entity
Public Class MvcApplication
Inherits System.Web.HttpApplication
Sub Application_Start()
AreaRegistration.RegisterAllAreas()
Database.SetInitializer(Of MusicStoreDB)(New DropCreateDatabaseAlways(Of MusicStoreDB)())
WebApiConfig.Register(GlobalConfiguration.Configuration)
FilterConfig.RegisterGlobalFilters(GlobalFilters.Filters)
RouteConfig.RegisterRoutes(RouteTable.Routes)
BundleConfig.RegisterBundles(BundleTable.Bundles)
AuthConfig.RegisterAuth()
End Sub
End Class
and the MusicStoreDB class
Imports System.Data.Entity
Public Class MusicStoreDB
Inherits DbContext
Public Property Albums() As DbSet(Of Album)
Get
End Get
Set(value As DbSet(Of Album))
End Set
End Property
Public Property Genres() As DbSet(Of Genre)
Get
End Get
Set(value As DbSet(Of Genre))
End Set
End Property
Public Property Artists() As DbSet(Of Artist)
Get
End Get
Set(value As DbSet(Of Artist))
End Set
End Property
End Class

Answer 1

Make sure your DbContext specifies the proper connection string:
public class MyNewContext : DbContext
{
public MyNewContext() : base("DefaultConnection")
{
}
public DbSet<Genre> Genres { get; set; }
public DbSet<Artist> Artists { get; set; }
public DbSet<Song> Songs { get; set; }
}
It is DefaultConnection by default, but make sure you changed yours to MusicStoreDB if you want to use your new connection string. I have left mine at default thus far and deployed to Azure effortlessly.
You should be able to use Entity Framework in a new project without setting up any new connection strings. It "just works" using SQL Express.
I'm willing to bet you have a database existing if you connect to (localdb)\v11.0 in SSMS or elsewhere.
Post your global.asax and DbContext if you continue to have problems.

Answer 2

So I faced this same problem today and it turns out that I presumed EF automatically checks on application start whether that DB exists or not; to say the least my hope was way to ambitious.
The EF will only create the DB if it doesn't exist once you invoke the DB context. For example when you first run the application, if on the landing page you don't instantiate the DB context nothing happens.
For the Music Store example if you are following the book, navigate to (using your own port number of course) "http://localhost:34295/StoreManager", that controller's action should instantiate the DBContext if you have been following the book.
Hope this helps anyone who got a little lost like me!