Document MVC and form-mapping differences

[halter73]

Documents that Minimal API and Blazor form mapping don't honor MVC model-binding attributes such as [BindNever] and [BindRequired].

Summary

• Adds warnings next to complex form-mapping guidance for Minimal APIs and Blazor.
• Recommends dedicated input models or DTOs to mitigate overposting.
• Clarifies form-mapping terminology in the Minimal API guidance.

Files changed

• aspnetcore/fundamentals/minimal-apis/includes/parameter-binding8-10.md: Documents unsupported MVC model-binding attributes and the recommended mitigation.
• aspnetcore/fundamentals/minimal-apis/parameter-binding.md: Updates article metadata.
• aspnetcore/blazor/forms/binding.md: Adds discoverable form-mapping attribute guidance and links to the existing overposting guidance.

---

Internal previews

File	Preview link
aspnetcore/blazor/forms/binding.md	aspnetcore/blazor/forms/binding
aspnetcore/fundamentals/minimal-apis/includes/parameter-binding8-10.md	aspnetcore/fundamentals/minimal-apis/includes/parameter-binding8-10

[wadepickett]

@halter73, Approved. Looks good. I will wait on merging since you also asked some other folks to take a look.

[guardrex]

Left suggestions to cross-link the namespace with the full name as link text.

[guardrex]

@halter73 @wadepickett ... For the Blazor article remarks, that doesn't seem like the best spot/approach for coverage. There's a dedicated section on [SupplyParameterFromForm] at Supply a parameter from the form ([SupplyParameterFromForm]). Shouldn't this be documented in that section with the remarks on that API? It also wouldn't need to be a NOTE in that position.

[javiercn]

Looks good to me. I wouldn't call it limitations but differences.