Investigate moving MVC Attributes from Microsoft.AspNetCore.Mvc namespace to Microsoft.AspNetCore.Http namespace

[rafikiassumani-msft]

With Minimal APIs we introduced different attributes such as Produces<T>, Consumes<T> as part of the Microsoft.AspNetCore.Http namespace. We would like to investigate the effort/trouble required to move the remaining MVC attributes (Consumes<T>, etc.) to Microsoft.AspNetCore.Http namespace and be consistent across both Minimal and MVC.

This could be both source and binary breaking.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[BrennanConroy]

Took a quick look at this and am not sure it's really feasible.

To start with we can look at the metadata defined in https://github.com/dotnet/aspnetcore/tree/main/src/Http/Http.Abstractions/src/Metadata and our goal would be to find attributes that implement these interfaces and move them from MVC to Http.
Many of the MVC attributes are defined in https://github.com/dotnet/aspnetcore/tree/main/src/Mvc/Mvc.Core/src and if we look at them we will see that nearly all of them also implement one or more MVC specific interfaces.
For example, the ConsumesAttribute

aspnetcore/src/Mvc/Mvc.Core/src/ConsumesAttribute.cs

Lines 21 to 26 in 05b2afb

	public class ConsumesAttribute :
	Attribute,
	IResourceFilter,
	IConsumesActionConstraint,
	IApiRequestMetadataProvider,
	IAcceptsMetadata

implements a resource filter and an action constraint, both of which are MVC specific features. It wouldn't make sense to move those interfaces to Http as well and we can't remove those from the attribute as MVC uses them.

Other attributes have similar problems, like FromBody implements IBindingSourceMetadata and IConfigureEmptyBodyBehavior.

It looks like unless we are willing to make huge breaking changes or move a lot of MVC specific interfaces into Http we can't move the public attributes from MVC to Http.