Skip to content

Merge to Live #37188

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wadepickett merged 1 commit into from
May 23, 2026
Merged

Merge to Live #37188

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 17 additions & 1 deletion aspnetcore/fundamentals/minimal-apis/includes/parameter-binding8-10.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,23 @@ For more information on XSRF attacks, see [Antiforgery with Minimal APIs](xref:s

For more information, see [Form binding in Minimal APIs](https://andrewlock.net/exploring-the-dotnet-8-preview-form-binding-in-minimal-apis/);

<a name="bindcc"></a>
#### IFormFile collection binding behavior

The following table summarizes how different <xref:Microsoft.AspNetCore.Http.IFormFile> collection parameter types are bound in Minimal APIs. The general guidance that the parameter name in the route handler must match the form field name applies to <xref:Microsoft.AspNetCore.Http.IFormFile> and supported named file collections such as <xref:System.Collections.Generic.IReadOnlyList%601>, but not to <xref:Microsoft.AspNetCore.Http.IFormFileCollection>, which binds all uploaded files.

| Parameter type | Bound value | Honors parameter name? |
| --- | --- | --- |
| [`IFormFileCollection`](xref:Microsoft.AspNetCore.Http.IFormFileCollection) | All files in [`HttpContext.Request.Form.Files`](xref:Microsoft.AspNetCore.Http.IFormCollection.Files) | No |
| [`IFormFile`](xref:Microsoft.AspNetCore.Http.IFormFile) | The single file whose form field name matches the parameter name | Yes |
| [`IReadOnlyList<IFormFile>`](xref:System.Collections.Generic.IReadOnlyList%601) | All files whose form field name matches the parameter name | Yes |
| Other [`IFormFile`](xref:Microsoft.AspNetCore.Http.IFormFile) collection types (`IEnumerable<IFormFile>`, `List<IFormFile>`, `IFormFile[]`, etc.) | Not supported — parameter is not populated | N/A |

Use <xref:Microsoft.AspNetCore.Http.IFormFileCollection> when you need all uploaded files regardless of form field name. Use <xref:System.Collections.Generic.IReadOnlyList%601> when you need only the files whose form field name matches the parameter name.

> [!NOTE]
> The <xref:Microsoft.AspNetCore.Http.IFormFile> collection binding rules in the preceding table also apply to properties on [`[AsParameters]`](xref:Microsoft.AspNetCore.Http.AsParametersAttribute) types and form-mapped complex types, since the form-mapping layer is shared with Blazor.

<a id="bindcc"></a>

## Bind to collections and complex types from forms

Expand Down
2 changes: 1 addition & 1 deletion aspnetcore/fundamentals/minimal-apis/parameter-binding.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ author: wadepickett
description: Learn how parameters are populated before invoking minimal route handlers.
ms.author: wpickett
monikerRange: '>= aspnetcore-7.0'
ms.date: 10/22/2025
ms.date: 05/22/2026
uid: fundamentals/minimal-apis/parameter-binding
ai-usage: ai-assisted
---
Expand Down
Loading