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
1. Next, you must deploy your solution to Azure before you can open
112
-
your logic app and review the resources for your serverless app,
112
+
the deployment template and review the resources for your serverless app.
113
113
114
114
## Deploy your solution
115
115
@@ -135,13 +135,13 @@ your function app.
135
135
136
136

137
137
138
-
When your solution starts deployment to your specified resource group,
138
+
When Visual Studio starts deployment to your specified resource group,
139
139
your solution's deployment status appears in the Visual Studio **Output** window.
140
140
After deployment finishes, your logic app is live in the Azure portal.
141
141
142
142
## Edit logic app in Visual Studio
143
143
144
-
After your solution deploys to your resource group,
144
+
Now that your solution is deployed to your resource group,
145
145
open your logic app with the Logic App Designer
146
146
so you can edit and change your logic app.
147
147
@@ -167,11 +167,11 @@ and then choose **OK**.
167
167
To create your Functions project and function with JavaScript, Python,
168
168
F#, PowerShell, Batch, or Bash, follow the steps in the article,
169
169
[Work with Azure Functions Core Tools](../azure-functions/functions-run-local.md).
170
-
If you're developing your Azure function with C# within your solution,
170
+
To develop your Azure function with C# inside your solution,
171
171
you can use a C# class library by following the steps in the article,
172
172
[Publish a .NET class library as a Function App](https://blogs.msdn.microsoft.com/appserviceteam/2017/03/16/publishing-a-net-class-library-as-a-function-app/).
173
173
174
-
## Build functions in Visual Studio
174
+
## Deploy functions from Visual Studio
175
175
176
176
Your deployment template deploys any Azure functions that you have in your solution
177
177
from the Git repo that's specified by variables in the `azuredeploy.json` file.
0 commit comments