ASP.Net MVC Question:

-Repository pattern is useful for decoupling entity operations form presentation, which allows easy mocking and unit testing.

-The Repository will delegate to the appropriate infrastructure services to get the job done. Encapsulating in the mechanisms of storage, retrieval and query is the most basic feature of a Repository implementation.

-Repository pattern is useful for decoupling entity operations form presentation, which allows easy mocking and unit testing.

-Most common queries should also be hard coded to the Repositories as methods. Which MVC.NET to implement repository pattern Controller would have 2 constructors on parameterless for framework to call, and the second one which takes repository as an input:

class myController: Controller
{
private IMyRepository repository;

// overloaded constructor
public myController(IMyRepository repository)
{
this.repository = repository;
}

// default constructor for framework to call
public myController()
{
//concreate implementation
myController(new someRepository());
}
public ActionResult Load()
{
// loading data from repository
var myData = repository.Load();
}
}