Should we standardize on the use MediaTypeHeaderValue in ActionResults?

[pranavkm]

We have seemingly different ways to specify ContentType \ Encoding in various ActionResults:

• ObjectResult uses MediaTypeHeaderValue https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNet.Mvc.Core/ActionResults/ObjectResult.cs#L32 👍
• FileResult allows specifying ContentType but not encoding (https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNet.Mvc.Core/ActionResults/FileResult.cs#L32)
• ContentResult allows specifying ContentType and Encoding separately - https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNet.Mvc.Core/ActionResults/ContentResult.cs#L16-L18
• ViewResult \ PartialViewResult allows specifying neither (Need a way to specify ContentType in ViewResult \ PartialViewResult #2408)

Might be more types here that I haven't looked at.

[rynowak]

In general the reason for the difference is what back-compat/legacy story each of these has. That's not to say we shouldn't consider improvements, but FileResult and ContentResult are more related to MVC 5, which didn't have a strongly-typed class for content-types.

[kichalla]

commit 7e62325