Razor pages handlers does not support IConvertToActionResult

[davhdavh]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.ExecutorFactory.CreateHandlerMethod(HandlerMethodDescriptor handlerDescriptor) only accepts void and IActionResult (and Task variants of same), but it does not support the already declared interface that lets your return type convert to an IActionResult, namely the Microsoft.AspNetCore.Mvc.Infrastructure.IConvertToActionResult.

Relevant code:
https://github.com/dotnet/aspnetcore/blob/main/src/Mvc/Mvc.RazorPages/src/Infrastructure/ExecutorFactory.cs#L28

Expected Behavior

Any class that implements IConvertToActionResult is a valid return value from razor page handler.

Steps To Reproduce

public class MyPageModel : PageModel {
   public ActionResult<bool> OnPostMyHandler() => true;
}

Exceptions (if any)

An unhandled exception occurred while processing the request.
InvalidOperationException: Unsupported handler method return type 'Microsoft.AspNetCore.Mvc.ActionResult1[System.Boolean]'. ​ Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.ExecutorFactory.CreateHandlerMethod(HandlerMethodDescriptor handlerDescriptor) ​ Stack Query Cookies Headers Routing ​ InvalidOperationException: Unsupported handler method return type 'Microsoft.AspNetCore.Mvc.ActionResult1[System.Boolean]'.
Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.ExecutorFactory.CreateHandlerMethod(HandlerMethodDescriptor handlerDescriptor)
Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.ExecutorFactory.CreateExecutor(HandlerMethodDescriptor handlerDescriptor)
Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvokerCache.GetHandlerExecutors(CompiledPageActionDescriptor actionDescriptor)
Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvokerCache.CreateCacheEntry(CompiledPageActionDescriptor compiledActionDescriptor, FilterItem[] cachedFilters)
Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageActionInvokerCache.GetCachedResult(ActionContext actionContext)
Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageRequestDelegateFactory+<>c__DisplayClass13_0.b__0(HttpContext context)
Microsoft.AspNetCore.Routing.EndpointMiddleware.Invoke(HttpContext httpContext)
Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+<>c__DisplayClass6_1+<b__1>d.MoveNext()
Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Session.SessionMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Session.SessionMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.OData.Batch.ODataBatchMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Diagnostics.StatusCodePagesMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)

.NET Version

since 2017

Anything else?

No response

[ghost]

To learn more about what this message means, what to expect next, and how this issue will be handled you can read our Triage Process document.
We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. Because it's not immediately obvious what is causing this behavior, we would like to keep this around to collect more feedback, which can later help us determine how to handle this. 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 work.

[ghost]

To learn more about what this message means, what to expect next, and how this issue will be handled you can read our Triage Process document.
We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. Because it's not immediately obvious what is causing this behavior, we would like to keep this around to collect more feedback, which can later help us determine how to handle this. 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 work.

[mkArtakMSFT]

Hi. Thanks for contacting us.
We're closing this issue as there was not much community interest in this ask for quite a while now.
You can learn more about our triage process and how we handle issues by reading our Triage Process writeup.