How can I send the model from MVC Controller Action to Razor Page (Asp.Net MVC Core 6.)?

Question

Hi,

How can I send the model from MVC Controller Action to Razor Page ? I am developing in Asp.Net MVC Core 6.

I added the view

This is the controller action

public async Task<IActionResult> ParamIndex(string path = "/locations/eng/", string apiKey = "")  
        {  
            ViewBag.SrvDtTime = DateTime.Now.ToString("MM/dd/yyyy HH:mm");  
            int franchiseId = 0;  
            int.TryParse(apiKey, out franchiseId);  
            FranchiseWidgetSetting? windgetSetting = null;  
            if (!string.IsNullOrWhiteSpace(path) || !string.IsNullOrWhiteSpace(apiKey))  
            {  
                windgetSetting = await _widgetSettingsRepository.FindFranchiseWidgetSettings(franchiseId, 0, apiKey, string.Empty, path);  
            }             
            return View("~/Views/Param/ParamIndex.cshtml", windgetSetting );  
        }  

this is the page view

@page "{path:string,apiKey:string}"  
@model RentalWidget.Views.Home.ParamWidget.ParamPageModel  
@using   RentalWidget.Models.DBEntities.Franchises  
@model FranchiseWidgetSetting  
@{  
  }  
  
<div id="SearchVehiclePage">  
    @await Html.PartialAsync("ParamSearchCar.cshtml",Model)  
</div>  

The Exception is related to Null Exception and It always return null.

This is the page model but it doesn't receive any debugger. I placed some debugger point in it but the debugger doesn't hit here.

public class ParamPageModel : PageModel  
    {  
        [BindProperty(SupportsGet = true)]  
        public string Path { get; set; } = "";  
  
        [BindProperty(SupportsGet = true)]  
        public string ApiKey { get; set; } = "";  
        public void OnGet()  
        {  
        }  
    }  

Either correct me or bring a good/recommended solution.
Thank you

Answer 1

Hi @mehmood tekfirst ,

You can try to convert the Razor pages to a MVC views, then in the controller, return the MVC view with the model.

Code like this:

Create a ParamModel: 231333-parammodel.txt

Controller: 231361-controller.txt

Right click the Param folder and add a MVC view (ParamIndex.cshtml):

Then the ParamIndex.cshtml like this: 231352-paramindex.txt

If you still want to use Razor Page, you can add the Razor Pages in the Pages folder, then in the controller, use the Redirect method to redirect to the Razor pages.

Code like this:

Controller:

return Redirect("/razorindex?path="+item.Path+"&apikey="+item.ApiKey);  

and in the razor page, the @page like this: 231362-paramrazorindex.txt

Then, in the Razor Page's Get method, receive the parameter, like this:

[Note] in this method, you need to register the Razor Page service and middleware.

The output like this: when access the Home controller Index action, it will redirect to the ParamRazorIndex Razor page.

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Best regards,
Dillion

Answer 2

Mvc controllers do not support calling razor pages instead of views. Your sample code is just using the razor page model as a view model, none of the methods will be called. The called razor view will just have a reference to this model and can use the properties like any view model.

Answer 3

The problem here which I shared in my above two posts is that passing Data property in ParamPageModel.

The community has explained several solutions. The problem is you do not understand web design fundamentals and therefore you do not understand the solutions provided by the community. You probably have heard HTTP is stateless? That's the problem you are trying to solve - maintaining state. Maintaining state is problem that exists in every web application that a web developers must deal with. Fortunately, there are many common methods for maintain state in a web application that you get to pick from; cookies, URL, session, database, etc.

The following line of code is an example of maintaining state in the URL; Path and apiKey.

return Redirect("parambooking/?path=" + item.Path + "&apikey=" + item.ApiKey);   

The redirect returns a HTTP 301 to the browser. The 301 has a location header that tells the browser where to make the next HTTP GET request which you set to parambooking/?path=somedata&apiKey=somedata. If you want to pass the Data object to parambooking then add parameters to the URL as I explained above. But this might not be the most effective way to maintain state between requests if Data is large. There is a limit to the length of a URL

A standard approach found in every beginning level tutorial is to pass the Id (primary key) of where the data exists in a database table. The logic on the parambooking fetches the data by Id. In MVC and Razor Page this is called the route parameter.

Routing to controller actions in ASP.NET Core
Configure a page route

Another option is storing Data in Session.

Session and state management in ASP.NET Core

Answer 4

There are several fundamental issues with your GitHib project. The sample project is missing the Razor Pages middleware. The Razor Page is within the View/Home folder which is the wrong location. By default Razor Pages are located in the Pages folder and the reason for the 404. The Razor page renders a partial but the partial is in the Home/View folder which is the wrong location too.

Lastly, your project does not properly maintain state as explained in this and your other threads on this subject.

Answer 5

I think either controller or razor pages should be used but not both at once.

It's odd to purposely use two different server side UI frameworks in the same project but it is possible to combine MVC and Razor Pages in a single web application. From my testing, the service order does not matter. What matters are the folders. Using a default configuration, Razor Page needs a Pages folder and MVC needs a Views folder as explained in my last post.

var builder = WebApplication.CreateBuilder(args);  
  
// Add services to the container.  
builder.Services.AddRazorPages();  
builder.Services.AddControllersWithViews();  
  
var app = builder.Build();  
  
// Configure the HTTP request pipeline.  
if (!app.Environment.IsDevelopment())  
{  
    app.UseExceptionHandler("/Home/Error");  
    // The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.  
    app.UseHsts();  
}  
  
app.UseHttpsRedirection();  
app.UseStaticFiles();  
  
app.UseRouting();  
  
app.UseAuthorization();  
app.MapRazorPages();  
app.MapControllerRoute(  
    name: "default",  
    pattern: "{controller=Home}/{action=ParamIndex}/{id?}");  
  
app.Run();  
  

The only thing left is to make sure you have Pages and View folders.