I use VS 2017. The visual part itself is perfectly published and available by url. But for some reason the database itself is not published. When creating a project, I used a local database and database first approach. What's the matter? What am I doing wrong, maybe the base should somehow be added separately to the openwork?

    2 answers 2

    LocalDB is most likely intended only for application testing during development. when publishing an application to the echo - you need to create a database with them

    example

    this is what they are writing Deploying the application to Azure To run the application in the cloud, follow these steps:

    Create an Azure cloud service. Create a SQL Azure database. Create an Azure Storage Account. Configure the application to use the Azure SQL database when it is running in the Azure cloud. Configure the application to use your storage account when running in Azure. Deploy the project to the Azure cloud service.

    but it also says that when testing an application through an echo a local database can be used, how to change the web config there is also written

    it has already been discussed like

      https://docs.microsoft.com/ru-ru/azure/app-service-web/web-sites-dotnet-deploy-aspnet-mvc-app-membership-oauth-sql-database

      Deploy the application to Azure

      In Visual Studio, right-click the project in Solution Explorer and select Publish from the context menu.

      enter image description here

      The Publish Website Wizard opens.

      Click the Settings tab on the left side of the Publish website dialog box.

      In the ApplicationDbContext section, select the database created when the project was created.

      In the ContactManagerContext section, select Execute Code First Migrations.

      enter image description here

      Click Publish.

      Log in as user1@contoso.com (with password P_assw0rd1) and make sure that you can change the data.

      Log out.

      Go to the Google Developer Console and on the Credentials tab, update the Redirect URI and JavaScript Orgins to use the Azure URL. Sign in with Google or Facebook. This will add a Google or Facebook account to the canEdit role. If you get an HTTP 400 error with the message The redirect URI in the request: https: // contactmanager {my version} .azurewebsites.net / signin-google didn’t match a registered redirect URI (redirect URI in the request https: // contactmanager {my version} .azurewebsites.net / signin-google does not match the registered redirect URI), you will have to wait for the changes to propagate.

      If this error appears for a few minutes, check that the universal resource codes are correct.