Should controllers in an ASP.NET MVC web app call repositories, services, or both?

Question

The controllers in my ASP.NET MVC web app are starting to get a bit bloated with business logic. The examples on the web all show simple controller actions that simply pull dat

Answer 1

It would help if we could stop seeing this example over and over again ...

public ActionResult Index()
{
  var widgetContext = new WidgetDataContext();
  var widgets = from w in widgetContext.Widget
                select w;
  return View(widgets);
}

I do realize that this isn't helpful to your question but it seems to be part of a lot of demo-ware that I think can be misleading.