Merge pull request #268044 from mattchenderson/httpattrib

adding HTTP output binding attribute for ASP.NET Core integration

Author: prmerger-automator[bot]

articles/azure-functions/dotnet-isolated-process-guide.md

@@ -311,11 +311,42 @@ To write to an output binding, you must apply an output binding attribute to the
 
 ### Multiple output bindings
 
-The data written to an output binding is always the return value of the function. If you need to write to more than one output binding, you must create a custom return type. This return type must have the output binding attribute applied to one or more properties of the class. The following example from an HTTP trigger writes to both the HTTP response and a queue output binding:
+The data written to an output binding is always the return value of the function. If you need to write to more than one output binding, you must create a custom return type. This return type must have the output binding attribute applied to one or more properties of the class. The following example is an HTTP-triggered function using [ASP.NET Core integration](#aspnet-core-integration) which writes to both the HTTP response and a queue output binding:
 
-:::code language="csharp" source="~/azure-functions-dotnet-worker/samples/Extensions/MultiOutput/MultiOutput.cs" id="docsnippet_multiple_outputs":::
+```csharp
+public class MultipleOutputBindings
+{
+    private readonly ILogger<MultipleOutputBindings> _logger;
+
+    public MultipleOutputBindings(ILogger<MultipleOutputBindings> logger)
+    {
+        _logger = logger;
+    }
+
+    [Function("MultipleOutputBindings")]
+    public MyOutputType Run([HttpTrigger(AuthorizationLevel.Function, "post")] HttpRequest req)
+    {
+        _logger.LogInformation("C# HTTP trigger function processed a request.");
+        var myObject = new MyOutputType
+        {
+            Result = new OkObjectResult("C# HTTP trigger function processed a request."),
+            MessageText = "some output"
+        };
+        return myObject;
+    }
+
+    public class MyOutputType
+    {
+        [HttpResult]
+        public IActionResult Result { get; set; }
+
+        [QueueOutput("myQueue")]
+        public string MessageText { get; set; }
+    }
+}
+```
 
-The response from an HTTP trigger is always considered an output, so a return value attribute isn't required.
+When using custom return types for multiple output bindings with ASP.NET Core integration, you must add the `[HttpResult]` attribute to the property that provides the result.
 
 ### SDK types
 

articles/azure-functions/functions-bindings-http-webhook-output.md

@@ -19,17 +19,15 @@ The default return value for an HTTP-triggered function is:
 ::: zone pivot="programming-language-csharp"
 ## Attribute
 
-Both [in-process](functions-dotnet-class-library.md) and [isolated worker process](dotnet-isolated-process-guide.md) C# libraries don't require an attribute. C# script instead uses a function.json configuration file as described in the [C# scripting guide](./functions-reference-csharp.md#http-output).
-
 # [Isolated worker model](#tab/isolated-process)
 
-A return value attribute isn't required. To learn more, see [Usage](#usage).
+A return value attribute isn't required when using [HttpResponseData]. However, when using a [ASP.NET Core integration](./dotnet-isolated-process-guide.md#aspnet-core-integration) and [multi-binding output objects](./dotnet-isolated-process-guide.md#multiple-output-bindings), the `[HttpResultAttribute]` attribute should be applied to the object property. The attribute takes no parameters. To learn more, see [Usage](#usage).
 
 # [In-process model](#tab/in-process)
 
 [!INCLUDE [functions-in-process-model-retirement-note](../../includes/functions-in-process-model-retirement-note.md)]
 
-A return value attribute isn't required. To learn more, see [Usage](#usage).
+A return value attribute isn't required for a [class library](functions-dotnet-class-library.md). C# script instead uses a function.json configuration file as described in the [C# scripting guide](./functions-reference-csharp.md#http-output). To learn more, see [Usage](#usage).
 
 ---
 
@@ -83,11 +81,21 @@ The following table explains the binding configuration properties that you set i
 To send an HTTP response, use the language-standard response patterns. 
 
 ::: zone pivot="programming-language-csharp"
-The response type depends on the C# mode:
+
+In .NET, the response type depends on the C# mode:
 
 # [Isolated worker model](#tab/isolated-process)
 
-The HTTP triggered function returns an [HttpResponseData](/dotnet/api/microsoft.azure.functions.worker.http.httpresponsedata) object or a `Task<HttpResponseData>`. If the app uses [ASP.NET Core integration in .NET Isolated](./dotnet-isolated-process-guide.md#aspnet-core-integration), it could also use [IActionResult], `Task<IActionResult>`, [HttpResponse], or `Task<HttpResponse>`.
+The HTTP triggered function returns an object of one of the following types:
+
+- [IActionResult]<sup>1</sup> (or `Task<IActionResult>`)
+- [HttpResponse]<sup>1</sup> (or `Task<HttpResponse>`)
+- [HttpResponseData] (or `Task<HttpResponseData>`)
+- JSON serializable types representing the response body for a `200 OK` response.
+
+<sup>1</sup> This type is only available when using  [ASP.NET Core integration](./dotnet-isolated-process-guide.md#aspnet-core-integration).
+
+When one of these types is used as part of [multi-binding output objects](./dotnet-isolated-process-guide.md#multiple-output-bindings), the `[HttpResult]` attribute should be applied to the object property. The attribute takes no parameters.
 
 [IActionResult]: /dotnet/api/microsoft.aspnetcore.mvc.iactionresult
 [HttpResponse]: /dotnet/api/microsoft.aspnetcore.http.httpresponse
@@ -110,3 +118,5 @@ For example responses, see the [trigger examples](./functions-bindings-http-webh
 ## Next steps
 
 - [Run a function from an HTTP request](./functions-bindings-http-webhook-trigger.md)
+
+[HttpResponseData]: /dotnet/api/microsoft.azure.functions.worker.http.httpresponsedata

articles/azure-functions/functions-bindings-http-webhook-trigger.md

@@ -510,11 +510,11 @@ def main(req: func.HttpRequest) -> func.HttpResponse:
 ::: zone pivot="programming-language-csharp"
 ## Attributes
 
-Both [in-process](functions-dotnet-class-library.md) and [isolated worker process](dotnet-isolated-process-guide.md) C# libraries use the `HttpTriggerAttribute` to define the trigger binding. C# script instead uses a function.json configuration file as described in the [C# scripting guide](./functions-reference-csharp.md#http-trigger).
+Both the [isolated worker model](dotnet-isolated-process-guide.md) and the [in-process model](functions-dotnet-class-library.md) use the `HttpTriggerAttribute` to define the trigger binding. C# script instead uses a function.json configuration file as described in the [C# scripting guide](./functions-reference-csharp.md#http-trigger).
 
 # [Isolated worker model](#tab/isolated-process)
 
-In [isolated worker process](dotnet-isolated-process-guide.md) function apps, the `HttpTriggerAttribute` supports the following parameters:
+In [isolated worker model](dotnet-isolated-process-guide.md) function apps, the `HttpTriggerAttribute` supports the following parameters:
 
 | Parameters | Description|
 |---------|----------------------|