ViewComponents | Declarative view components | Model View Controller library

I am rewriting/ moving a website from ASP MVC to ASP MVC Core. This application has a dynamic menu which depends on the logged in user. In order to build the menu, each controller derives from a custom BaseController who sets in ViewBag menu items, an later, in Layout, those items are retrieved and passed as arguments to a PartialView.

I understand that in .Net Core 3.1 that the html.action was removed in favor of ViewComponents. Unfortunately the code I have does not lend itself for a ViewComponent since it is a custom PeoplePicker control that will have user interaction. Keep in mind that this PeoplePicker control works correctly in .Net 4.7.2. I've looked on line and found methods on how to re-implement the html.action functionality. The problem I'm having is that when the code hits the await invoker.InvokeAsync(); line in the code the ActionContext that was set gets overwritten by subsequent calls to the underlying model's get/set properties. I'll walk through the code and what is happening. Here is the line that calls the PeoplePicker:

I am trying to create a general purpose Delete Confirmation dialogue screen for deleting the record . I have created a component file as Delete razor page to call from other MVC controller as re-use of razor page. Here is my code Confirm.razor

I'm currently building and application in ASP.NET Core MVC and I have ran into a problem which I cannot solve.

I have a form for something and that form should contain multiple identical fields which are added dynamically (1-10). I have managed to do that by creating a ViewComponent which contains those form fields and I make an Ajax call to invoke the view component into a tab if a user chooses to add another segment of those fields.

I'm just getting to grips with ViewComponents in my Razor pages application.

I have a ViewComponents folder within my project that contains my ViewComponent .cs code:

I'm currently trying to load embedded ViewComponents from external assemblies.

I've included this in my project file:

I am trying to learn the right use of a ViewComponent in ASP.NET Core Mvc, so I have the following example: The idea is to render a view with Movie details, and inside it, the "ReviewViewComponent" holding a 10-star movie rating widget.

Inside the ViewComponent's View is actually a form with radio buttons. The form action name is passed to the ViewComponent (either "Create" or "Edit", depending on if the user already gave a rating). Depending on the received action name, the form inside the ViewComponent will either call the Create or the Edit method inside ReviewsController.

This all works until I reach the return call inside ReviewsController. I would like to be able to return the ViewComponent there and simply render the return result inside the div with id="now-showing-details-rating-div" in Details using ajax. This works with PartialViews (code commented out in ReviewsController edit method), but it seems it doesn't work with ViewComponents (it just renders the ViewComponent View as a completely new View, even though I call the ajax on the form the same way I would do if it were in a PartialView).

Am I actually misusing the ViewComponent concept here? In the sense of rendering a portion of a View after form submit, is it actually better to just use PartialViews?

Ajax snippet

I created a ViewComponent class which call a REST API using the HttpClient, this is the code:

I've created a ViewComponent to show Popups in my WebApp, this VC is only used as a shell for html (using bootstrap modals) and the popup content is loaded via javascrit from a Partial Page.

When I try to use asp-for tag helpers in the content of the partial, I get this error: