Database First DBContext在本地工作，但在部署时无法工作

Question

I deployed a webapi project to azure that connects to a database via a DbContext. Everything works locally but when I deploy I am hit with an error anytime I make a request that will need to access my DbContext.

I open a connection as follows:

 public ProductRepo(ProdStoreEntities context)
        {
            dbContext = context;
            dbContext.Database.Connection.Open();
        }

My web.config is as follows:

<connectionStrings>
   <add name="DefaultConnection" connectionString="Data Source=(LocalDb)\v11.0;AttachDbFilename=|DataDirectory|\aspnet-CatalogAPI-20160227031830.mdf;Initial Catalog=aspnet-CatalogAPI-20160227031830;Integrated Security=True" providerName="System.Data.SqlClient" />
    <add name="ProdStoreEntities" connectionString="metadata=res://*/DbCache.csdl|res://*/DbCache.ssdl|res://*/DbCache.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=.\SQLEXPRESS;initial catalog=ProdStore;integrated security=True;MultipleActiveResultSets=True;App=EntityFramework&quot;" providerName="System.Data.EntityClient" />
  </connectionStrings>

I would have thought that everything would be handled for me since I am using a DbContext but when I deploy and attempt to make a get request that would require a database query I recieve the following error:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Any ideas on why this might be happening? I haven't done anything special when publishing, I literally right click my class libray and hit publish. I initally generated the DbContext via a database first approach if that matters.

Answer 1

This could be from a few things.

Check that you are running Localdb on your deployment server

Secondly, check that the database has been intialized on the deployed server.

Thirdly, are you able to to login to the database via management studio via the credentials you're providing - Make sure your user details has the privileges on the deployed server to access the database

Answer 2

Your problem is that your connection string says that it is a local database. what you have to do is create a database in Azure, when you have done that you can actually see a connection string to that database, that connection string needs to replace your current connection string where you have your (local) db