You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert

49
48
50
49
The **Change Authentication** dialog appears.
51
50
52
51
* Select **Individual User Accounts**.
53
-
* Select **OK** to return to the **New ASP.NET Core Web Application**, then select **OK** again.
52
+
* Select **OK** to return to the **New ASP.NET Core Web Application**, then select **Create**.
54
53
55
54

56
55
@@ -59,22 +58,22 @@ Visual Studio creates the solution.
59
58
## Run the app
60
59
61
60
* Press CTRL+F5 to run the project.
62
-
* Test the **About**and **Contact** links.
61
+
* Test the **Privacy**link.
63
62
64
63

65
64
66
65
### Register a user
67
66
68
67
* Select **Register** and register a new user. You can use a fictitious email address. When you submit, the page displays the following error:
69
68
70
-
*"Internal Server Error: A database operation failed while processing the request. SQL exception: Cannot open the database. Applying existing migrations for Application DB context may resolve this issue."*
69
+
*"A database operation failed while processing the request. Applying existing migrations for Application DB context may resolve this issue."*
71
70
* Select **Apply Migrations** and, once the page updates, refresh the page.
72
71
73
-

72
+

74
73
75
-
The app displays the email used to register the new user and a **Log out** link.
74
+
The app displays the email used to register the new user and a **Logout** link.
76
75
77
-

76
+

78
77
79
78
## Deploy the app to Azure
80
79
@@ -84,53 +83,76 @@ Right-click on the project in Solution Explorer and select **Publish...**.
84
83
85
84
In the **Publish** dialog:
86
85
87
-
* Select **Microsoft Azure App Service**.
88
-
* Select the gear icon and then select **Create Profile**.
In the **Publish** dialog select **Create a new Azure App Service...**
99
+
100
+

94
101
95
102
The **Create App Service** dialog appears:
96
103
97
-
* Enter your subscription.
98
104
* The **App Name**, **Resource Group**, and **App Service Plan** entry fields are populated. You can keep these names or change them.
105
+
* Select **Create**.
106
+
107
+

108
+
109
+
After creation is completed the dialog is automatically closed and the **Publish** dialog gets focus again:
99
110
100
-

111
+
* The new instance that was just created is automatically selected.
112
+
* Select **Finish**.
101
113
102
-
* Select the **Services** tab to create a new database.
114
+

103
115
104
-
* Select the green **+**icon to create a new SQL Database
116
+
Next you see the **Publish Profile summary**page. Visual Studio has detected that this application requires a SQL Server database and it's asking you to configure it. Select **Configure**.

131
+
The **Create Azure SQL Database** appears:
120
132
121
-
* Select **OK**.
133
+
* The **Database name**, **Resource Group**, **Database server** and **App Service Plan** entry fields are populated. You can keep these values or change them.
134
+
* Enter the **Database administrator username** and **Database administrator password** for the selected **Database server** (note the account you use must have the necessary permissions to create the new Azure SQL database)
135
+
* Select **Create**.
122
136
123
-
Visual Studio returns to the **Create App Service**dialog.
* The new instance that was just created is automatically selected.
142
+
* Select **Next**.
128
143
129
-
Visual Studio creates the Web app and SQL Server on Azure. This step can take a few minutes. For information on the resources created, see [Additional resources](#additional-resources).
In the next step of the **Configure Azure SQL Database** dialog:
132
147
133
-

148
+
* Enter the **Database connection user name** and **Database connection password** fields. These are the details your application will use to connect to the database at runtime. Best practice is to avoid using the same details as the admin username & password used in the previous step.
0 commit comments