Bring back Controller.TryUpdateModel

[davidfowl]

No description provided.

[divega]

+1

[pranavkm]

A couple of questions about this:

1. In Mvc 5, the Controller type had special knowledge about things like ValueProviders, ModelMetadataProvider etc. This is not true in Mvc 6. There doesn't seem to be specific reasons to hanging this off of the Controller in particular if we want to support POCO controllers. Is there a better location to hang this off of - for instance the https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNet.Mvc.Core/ParameterBinding/IActionBindingContextProvider.cs\ ActionBindingContext or something along those lines?
2. There's about a dozen overloads of this method in Mvc 5 (http://msdn.microsoft.com/en-us/library/system.web.mvc.controller.tryupdatemodel(v=vs.118).aspx). Are all the overloads necessary?

[pranavkm]

Bump?

[pranavkm]

1. We need to expose on controller, but also such that it's easy enough to do in a POCO controller.

[pranavkm]

@DamianEdwards @davidfowl do you have preferences or explicit list of which of these 10 overloads are useful?

[RoboBurned]

Microsoft.AspNetCore.All 2.1.5
The name 'TryUpdateModel' does not exist in the current context

[pranavkm]

@RoboBurned, it's TryUpdateModelAsync - https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.controllerbase.tryupdatemodelasync?view=aspnetcore-2.1#Microsoft_AspNetCore_Mvc_ControllerBase_TryUpdateModelAsync_System_Object_System_Type_System_String_

[RoboBurned]

@pranavkm, I see async version, but there is no TryUpdateModel.
I will use this approach even if it looks more complicated.
TryUpdateModelAsync(user, ...).GetAwaiter().GetResult();

[pranavkm]

Use await TryUpdateModelAsync(...); in your controller action. Doing a blocking call (GetResult) may result in thread pool starvation and application deadlocks.

[RoboBurned]

@pranavkm I cannot use await because my action is not async

[davidfowl]

@RoboBurned make the action asynchronous instead.