Home/ Questions/Q 6166845
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T22:24:38+00:00

I am using: Asp.net MVC3 Ninject Repository pattern with Entity Framework 4.0 On an

  • 0

I am using:

  • Asp.net MVC3
  • Ninject
  • Repository pattern with Entity Framework 4.0

On an admin page there is a select where the user can choose a product group.
The dropdown is in a partial view in EditorTemplates. The partial view today handles the data access itself. My question is, what is the best practice for this partial view?

Is it:

  1. Keep it as it is
  2. Move the select to a view that is rendered by an Action, so that the Controller can get its dependencies from Ninject
  3. The Partial View gets both the ID of the product group selected AND all the groups from the view that invokes it.
  4. ?

Above i described a specific scenario, but I guess that it is a common problem, and I haven’t found a good way of doing it on SO.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    As long as the partial view is called once, I’d go with option 2. I’d look into MiniProfiler to see all the calls to the database. You shouldn’t be doing much of that if any in your views. If it’s being called for each item in the select or if you have the data already, it would be faster to pass that data directly to the view.

    • 0