如何在ASP.NET MVC Core的ManageController中使用CarsContext？

Got it, let's break this down into two clear parts since you have two separate needs here: using CarsContext in ManageController and handling the call to CarsController's Index method.

You don't need to manually instantiate CarsContext with DbContextOptions<CarsContext>—ASP.NET Core's dependency injection system handles that for you. Just inject CarsContext directly into ManageController's constructor, same way you're already using UserManager and SignInManager.

Here's how to modify your ManageController:

public class ManageController : Controller
{
    private readonly UserManager<ApplicationUser> _userManager;
    private readonly SignInManager<ApplicationUser> _signInManager;
    private readonly CarsContext _carsContext; // Add this field

    // Update constructor to include CarsContext
    public ManageController(
        UserManager<ApplicationUser> userManager,
        SignInManager<ApplicationUser> signInManager,
        CarsContext carsContext) // Inject here
    {
        _userManager = userManager;
        _signInManager = signInManager;
        _carsContext = carsContext; // Assign to field
    }

    // Example action that uses CarsContext
    public async Task<IActionResult> MyCars()
    {
        // Fetch car data using the injected context
        var cars = await _carsContext.Cars.ToListAsync();
        return View(cars);
    }
}

This works because you already set up CarsContext in your Program.cs (or Startup.cs for older versions) when you scaffolded the CarsController—the DI system knows how to create and inject it.

You shouldn't directly call another controller's action method like a regular class method—controllers are designed to be instantiated by the ASP.NET Core framework, and direct calls might skip important pipeline steps (like model binding, filters, etc.). Instead, use one of these better approaches:

Option 1: Redirect to the Cars Index action #

If you just want to send the user to the Cars Index page from a ManageController action, use RedirectToAction:

public IActionResult GoToCars()
{
    // Redirect to CarsController's Index method
    return RedirectToAction("Index", "Cars");
}

Option 2: Reuse the business logic (better for sharing data) #

If you need to display car data within a ManageController view (instead of sending the user to the Cars page), extract the data-fetching logic from CarsController into a separate service class. This way both controllers can use the same logic without duplication.

First, create a service interface and class:

public interface ICarService
{
    Task<List<Car>> GetAllCarsAsync();
}

public class CarService : ICarService
{
    private readonly CarsContext _context;

    public CarService(CarsContext context)
    {
        _context = context;
    }

    public async Task<List<Car>> GetAllCarsAsync()
    {
        return await _context.Cars.ToListAsync();
    }
}

Register the service in Program.cs:

builder.Services.AddScoped<ICarService, CarService>();

Then inject this service into both controllers:

• In CarsController:

  public class CarsController : Controller
  {
      private readonly ICarService _carService;
  
      public CarsController(ICarService carService)
      {
          _carService = carService;
      }
  
      public async Task<IActionResult> Index()
      {
          var cars = await _carService.GetAllCarsAsync();
          return View(cars);
      }
  }
  

• In ManageController:

  public async Task<IActionResult> ManageWithCars()
  {
      var cars = await _carService.GetAllCarsAsync();
      // Pass cars to your Manage view, maybe along with user data
      var viewModel = new ManageWithCarsViewModel
      {
          User = await _userManager.GetUserAsync(User),
          Cars = cars
      };
      return View(viewModel);
  }
  

This keeps your code DRY (Don't Repeat Yourself) and follows best practices for separation of concerns.

Option 3: Return the Cars Index view directly (not recommended) #

If you really need to return the Cars Index view from ManageController without redirecting, you can do it—but note that this skips the CarsController's Index action logic. Only use this if the Cars view doesn't depend on any logic from CarsController:

public async Task<IActionResult> ShowCarsFromManage()
{
    var cars = await _carsContext.Cars.ToListAsync();
    // Return the Cars/Index view with the data
    return View("~/Views/Cars/Index.cshtml", cars);
}

But again, this is not ideal because it bypasses the controller's action pipeline. Reusing a service is the better approach.

内容的提问来源于stack exchange，提问作者koviroli