@@ -55,7 +55,7 @@ This example shows a [C# function](dotnet-isolated-process-guide.md) that receiv
55
55
56
56
This example uses an HTTP trigger with an ` OutputType ` object to both send an HTTP response and write the output message.
57
57
58
- ``` cs
58
+ ``` csharp
59
59
[Function (" HttpSendMsg" )]
60
60
public async Task < OutputType > Run ([HttpTrigger (AuthorizationLevel .Function , " get" , " post" )] HttpRequestData req , FunctionContext context )
61
61
{
@@ -74,7 +74,7 @@ public async Task<OutputType> Run([HttpTrigger(AuthorizationLevel.Function, "get
74
74
75
75
This code defines the multiple output type ` OutputType ` , which includes the Service Bus output binding definition on ` OutputEvent ` :
76
76
77
- ``` cs
77
+ ``` csharp
78
78
public class OutputType
79
79
{
80
80
[ServiceBusOutput (" TopicOrQueueName" , Connection = " ServiceBusConnection" )]
@@ -88,7 +88,7 @@ This code defines the multiple output type `OutputType`, which includes the Serv
88
88
89
89
The following example shows a [ C# function] ( functions-dotnet-class-library.md ) that sends a Service Bus queue message:
90
90
91
- ``` cs
91
+ ``` csharp
92
92
[FunctionName (" ServiceBusOutput" )]
93
93
[return : ServiceBus (" myqueue" , Connection = " ServiceBusConnection" )]
94
94
public static string ServiceBusOutput ([HttpTrigger ] dynamic input , ILogger log )
@@ -97,13 +97,12 @@ public static string ServiceBusOutput([HttpTrigger] dynamic input, ILogger log)
97
97
return input .Text ;
98
98
}
99
99
```
100
-
101
100
  ;
102
101
<hr />
103
102
104
103
Instead of using the return statement to send the message, this HTTP trigger function returns an HTTP response that is different from the output message.
105
104
106
- ``` cs
105
+ ``` csharp
107
106
[FunctionName (" HttpTrigger1" )]
108
107
public static async Task < IActionResult > Run (
109
108
[HttpTrigger (AuthorizationLevel .Anonymous , " get" , " post" , Route = null )] HttpRequest req ,
0 commit comments